Local

Website builder server (On-premises only) requirements

• Web server: Apache / Nginx / LiteSpeed
• Backend: PHP, MySQL, ionCube
• Hardware: CPU 2GHz, 20 GB (HDD or SSD), 2 GB RAM
• OS: Ubuntu, Debian, CentOS, Windows and others

Published websites requirements

• Web Server: Apache / Nginx / LiteSpeed / Microsoft IIS
• Backend: PHP
• Hardware: any
• OS: any

Yes, you can have multiple On-premises website builder installations on 1 server.
You need to create a separate brand for each installation.

1. Go to My Licenses;
2. Click "Add brand";
3. Select "On-Premises" brand;
4. Click "Manage" button;
5. Click "Builder installation / update" and follow installation guide.

Note: Each brand must have a different hosting server IP assigned to it.

In order to move website builder to a different server you need to take the following steps:

1. Prepare new place for website builder so it meets website builder installation guide requirements;
2. Move website builder files to a configured virtual host on a new server (make sure that moved files on a new server have correct permissions);
3. Move website builder database and its data to a new server;
4. Set up website builder cron command by documentation docs/builder/cron/;
5. Make sure that website builder files and website builder database are working together on a new server:
   • If website builder database connection credentials are changed on a new server, update them also in website builder configurational files "config.json" (it is located in website builder root folder) in "db" section;
   • If IP of new website builder server is changed, make sure that this IP is not blocked by firewall (on FTP ports [20, 21, passive ports] and HTTPS ports [80, 443]) on your hosting servers where you use website builder plugin.
6. Go to licenses page licenses4, expand the brand by clicking button "Expand" and click "Apply" button in the bottom of the dialog to re-sync brand data with your website builder installation. If the dialog is closed with no warnings then it means that the website builder has no issues.

Why it can happen?

The client may accidentally choose another template or reset existing template to default one in website builder. Note, that this action removes current client's project. However, there are two methods to restore it.

Two options to restore a reset website

1. Open website builder for this website, expand "Publish" menu and choose "Backup/Restore" option. Switch to tab "Restore". There you may see some auto-saved backups of earlier website state saved. Try choosing the oldest one and click "Restore" button. After that check if it has been restored.
2. If website cannot be restored via the first option, but you have correct live published website, then you can restore website in website builder from published website. Take following steps:
• Empty client's folder in website builder that holds client's current project data/e/x/example.com/ (where client's domain is "example.com" and part "/e/x/" is 1st and 2nd domain's letters)
• Copy folders "sitepro/dat" and "sitepro/gallery" into client's project folder in website builder, so that copied folders are located in:
• data/e/x/example.com/dat
• data/e/x/example.com/gallery
• Update permissions of copied folders if needed.

Once done, you should see last version of client's published website in website builder when reloading it.

Note: that even if the reset website was published, then you may try to firstly restore client's account on hosting to an earlier state where the live website was correct, and then restore website in website builder following steps from the second option.

In On-Premises website builder installation while the customer is inside website builder editing his website, auto-backups are being saved automatically when draft is saved. It happens when the client clicks button "Save draft", "Publish" and "Download backup".
The data of all auto backup is saved in website builder installation in website project folder, e.g.: [builder]/data/e/x/example.com/backups (here we assume that domain is "example.com" and the part "/e/x/" is the 1st and 2nd letters of domain name).
By default, auto backups are saved every 5 minutes and only if changes are made to the project. The number of auto-backups per website is limited to 50 copies by default. When the limit of copies is reached, the process of saving is continued by removing oldest copies and only keeping 50 newest.

With each auto backup saving, website builder saves only data, but not the whole project, thus saving space on disk. 50 copies in total may take slightly more of disk space than the original project.

Default values — interval of 5 minutes and number of 50 copies — can be changed in On-Premises brand configuration to any values. Also there is an option to disable auto backups saving at all.

For On-Premises brand only:
To create custom templates for your clients:

1. Go to your license page: My-Licenses, click on "Manage";
2. Install website builder;
3. Select "Custom templates" (on black toolbar);
4. Follow templates’ creation instruction;
5. Save and apply the customized templates for your brand.

Make sure that you clicked "Apply" button in your On-Premises brand after builder installation. If you clicked it and website builder is still throwing error "Authorization required", take the following steps to fix it:

Method 1:

Check if API username and password that you entered during website builder installation are correct.

1. Open website builder file "config.json" located in website builder web root folder.
2. Locate parameters "apiUsername" and "apiPassword".
3. Make sure they are the same as specified in On-Premises brand.
4. Fix them if needed (if password in the license contains symbols "/" please replace it with "\/" in "config.json" file) and save the file.
5. Click "Recheck" button in On-Premises brand to see if the problem was resolved.

Method 2:

If method 1 did not help, try the following:

1. Open file ".htaccess" located in website builder web root folder.
2. Comment line below:
   RewriteRule ^(.*)$ index.php [L,QSA]
   
3. Uncomment line:
   #RewriteRule ^(.*)$ index.php?HTTP_AUTHORIZATION=%{HTTP:Authorization} [L,QSA]
4. Save file.
5. Open file "config.json".
6. Add parameter "keepHtaccess": true somewhere in the middle and save the file.
7. Click "Recheck" button in On-Premises brand to see if the problem was resolved.

"No fonts available at the moment" message is shown only in case google fonts API responds with an error to website builder requests and there is no cached version of a previous good response.

There are two possible conditions depending on your situation.

If you have googleFontsApiKey entered in your website builder config.json.

Please make sure that:

• googleFontsApiKey entered in website builder config.json is correct;
• the key permissions allow using it from website builder server IP;
• the key may be used with google fonts API.

You have google maps API key configured and no google fonts API key.

In that case website builder will use google maps API key for google fonts. Please make sure that:

• the google maps API key permissions allow using it from website builder server IP;
• the key may be used with google fonts API.

In order to migrate from On-Premises to Cloud brand you need to take the following steps:

1. Add IP to Cloud brand:
   • Navigate to My Licenses page;
   • Select brand with website builder location "Your own server", and click button next to "Servers' IPs";
   • Temporarily save all your IP addresses in a text document and remove them from the "Your own server" brand;
   • Click "Apply" button to save changes;
   • Click "Add brand" button;
   • Select one of your preferred website builder location servers (except "Your own server");
   • Click "Save" button;
   • Choose your new Cloud brand and click button next to "Servers' IPs";
   • Insert your copied IP addresses;
   • Click "Apply" button to save changes.
2. Contact us to transfer websites:
   • Contact our support team and we will transfer websites for you;
   • Once all of websites will be transferred, our team will notify you.
3. Reinstall plugins:
   • Navigate to My Licenses page;
   • Click button next to "Hosting Panel/Billing Panel";
   • Click on needed panel (e.g., cPanel or WHMCS) to access the documentation;
   • Follow the instructions in the documentation to complete installation process;
   • Open all live websites in the Cloud brand from your hosting panel and republish them.

If you are encountering "Input required for method 'requestLogin'" error after updating website builder domain in your On-Premises brand, particularly when switching from "http" to "https", this error arises because plugin is unaware of changes you've made to domain, and it continues to call old website builder domain. In this blog post, we will delve deeper into this issue, understand why it happens, and provide a step-by-step guide on how to resolve it.
To fix problem just re-install plugin following installation guide in your brand (or direct link).

For On-Premises brand only:
If you want to update PHP version for website builder, please refer this page:
Changing PHP version.

• If you are running website builder under Apache server, most probably .htaccess in website builder is not working. Check if apache module "mod_rewrite" is turned on.
  In case you are using nginx server, you need to additionally configure website builder by this instruction (section "Configuration for builder");
• Make sure that website builder domain is resolved to a correct IP address on your website builder server;
• Make sure that you have correct value for API URL defined by parameter siteProApiUrl in website builder configurational file ("config.json") located in website builder installation root folder.

• Website builder cannot be accessed directly by URL, for example: http://builder.mysite.com. It can be opened only via public demo URL (that you can find you your brand) or via website builder plugin installed on hosting panel;
• In case error URL of page contains part similar to "?login_hash=a1b2c3...", it means that you have wrong website builder plugin installed on your hosting or you installed it before website builder installation. You need to delete it and install plugin anew using plugin installation guide link from On-Premises brand.
• Also, please check website builder files owner and group. If you extracted website builder archive from SSH terminal being logged in as root, you need to chown files to a correct user and group.

If the problem occurred right after website builder installation or update, the reason may be in:

• Improper website builder version used during installation/update (there are two versions — for PHP 5.6 or lower and for PHP 7 or higher). To fix this problem make website builder manual update. Please find instruction on your On-Premises brand page ("Builder installation guide" -> "Update" section).
• Improper website builder archive extraction — possibly not all files were successfully extracted which lead to website builder crash.
  To fix this problem make website builder manual update.
• File ".htaccess" located in website builder web root directory. Possibly some directives (like "Options" or "DirectoryIndex") are not allowed by your hosting and it ends with error 500. Make sure that hosting settings let to use/overwrite these options.

Another reason can be logged in file "error_log" in web root folder of website builder. Please check if this file exists and that the new output is written once you get error 500. According to error, you can determine what causes this error to happen.