I used sitejet builder with cpanel to build and publish my website. since lase 8-10 days I am not able to publish the website from sitejet builder interface. I am getting the error - The publication process is not available during website migration. Try again later or contact your hosting provider for assistance.
I cannot update my website. I am really stuck here and need help with the publishing.
CPanel version - 130.0.16
website domain has dedicated root directory.
Hey there,
Did you contact your hosting provider already?
For a better understanding of your case, we need more information according to our guidelines: 🔷 Guidelines - Ask your question the right way – and get the best answer faster!
Hello, Andre!
Yes. I connected by service provider Bigrock.in multiple times and their support staff always told me that the support for the cpanel+sitejet is not under their umbrella. Sitejet is available as part of CPanel and not exclusively offered by Bigrock. Last I could publish my website was on November 30. As of this moment I am able to edit the website but not able to publish it.
I am left with knocking doors from Bigrock to CPanel to sitejet.
I need a serious help on this.
Thanks in advance.
Hello Andre,
Can you or anyone from sitejet side please guide me to resolve the issue? Thanks in advance.
Hi Infotech!
A few questions arise:
- Did you move from one service provider to another?
- Did your host change their servers?
- Are your DNS records correct?
The above are all questions that only your hosting company can answer. It looks like the migration is not complete. If I look at the error, I can only think that the problem is with your host. It is highly unlikely that this will be a cPanel error.
See this (Ai assisted) search result:
Click to open
Website migration in cPanel is the process of moving a website (files, databases, settings) from one server or host to another, often using cPanel’s built-in Transfer Tool or manual backup/restore methods, to switch providers, upgrade servers, or change domains, ensuring minimal downtime and data integrity. It involves exporting data from the old cPanel account and importing it to the new one, then updating DNS records to point to the new server.
Key Methods
- cPanel Transfer Tool (WHM): Ideal for server-to-server moves, this automated tool in WebHost Manager (WHM) copies entire cPanel accounts (files, emails, databases, settings) from one server to another, reducing manual errors and downtime.
- Manual Migration (cPanel Backup/Restore): For moving individual sites or when full account transfer isn’t feasible, you manually:
- Backup: Create a full cPanel backup (.tar.gz) or export files/databases via FTP/phpMyAdmin from the old host.
- Upload: Transfer these backup files to the new server.
- Restore: Restore the backup or manually create/import databases and update configuration files (like wp-config.php for WordPress) with new credentials.
- DNS Update: Change the domain’s Name Servers (NS records) at the registrar to point to the new host.
Common Reasons for Migration:
- Changing Hosts: Moving to a provider with better performance, support, or pricing.
- Upgrading Servers: Transferring to a more powerful server for better speed and reliability.
- Platform Changes: Moving between different control panels (e.g., cPanel to Hostinger’s hPanel).
- Domain Changes: Migrating to a new domain name for rebranding or consolidation.
Key Steps & Considerations
- Pre-migration Checks: Clean up old files, update CMS versions (like WordPress), and ensure compatibility with new server software.
- DNS Propagation: Allow time for DNS changes to update globally after the migration.
Testing: Thoroughly test the site on the new server before making it live.
We can’t, because this seems an issue with your provider and cPanel. Did you contact their support already? It seems that there was something not completed when migrating to your server.
Your provider needs to contact cPanel and they need to fix this issue.
But keep us updated!
Yes, I’ve experienced the same behavior before.
My hosting provider told me that cPanel republishes the entire site on every publish (not only the changes), so on slower or shared hosting this can easily lead to timeouts.
This usually happens more often on larger projects or during migrations.
In most cases, the solution is either waiting until migration is fully completed or asking the hosting provider to increase execution / timeout limits, or use a faster hosting setup.
Came across the same error and upon checking error logs found an issue with tmp file (Ex: sitejet_domain) generated by SiteJet in cPanel > File Manager > tmp > locks folder. Seems like the file was generated and not removed during previous publish hence Sitejet could not create a new file to publish again. Renamed the file and the site was published successfully.
Hope this helps someone
2 Likes
I did forward this to the devs at cPanel to check on this.
As far as I can see, cPanel does clean up the locks during any issue in publishing. So, next time you try, the locks are located at $homedir/tmp/locks/sitejet_$domain
$homedir → cPanel user’s homedir
$domain → published domain
… and should be cleared up.
They will however double check and see if this brings any new light into this issue.