HTTP 500 Error
Hi,
I have restored a account from a backup, and before the site goes live I have tried to test my site by amending the local host file to recognise the fqdn
I tried to navigate to the test site and I am getting error
HTTP Error 500
I have checked the logs and nothing is appearing
Can someone help?
-
The IP address is assigned 0 -
A single website won't open on that shared IP, its a shared IP. If you want a single website to open on it, you'll need to assign that IP address to the account. It's not.
Would I need a separate IP for the support side? or can they all work on the same IP0 -
They can all work on the same IP address. That's why it's called a shared IP. :) The IP address is assigned
That shows all accounts on the same, shared IP address. This is fine, but your hosts file change to view the website at ip.add.res/~username will not work because:Detected mod_ruid2 in use. Using both mod_userdir and mod_ruid2 is not a supported configuration. Changes were not saved.
As we discussed back on page one of this thread.0 -
So if??? I change the external IP addresses from the live site to the new site the new site should work? 0 -
Is this what you are talking about 0 -
So if??? I change the external IP addresses from the live site to the new site the new site should work?
The nameservers at your Registrar, yes. Your old server has it's own nameservers for the domain. Your new server has it's own nameservers. Under normal circumstances, once you restore the account on the new server properly, and then update the domain name at your Registrar to use the new nameservers on the new server, yes, the site should work. Your main domain, is using cloudflare. If the support sub.domain is using cloudflare as well, you might consider disabling it and making sure the normal setup works as expected first, and then enable cloudflare once again.0 -
Is this what you are talking about
Yes.0 -
Thank you 0 -
The support sub domain is not covered by cloud flare that is why it has a ssl cert installed 0 -
I have had a response from our host providers, and they have given me this response regarding the HTTP 500 error Restoring a full backup does not restore the EasyApache profiles, only the site files and databases. EasyApache is the wizard in WHM which configures the Apache server and installs modules for you - if you visit this interface in the old server there may be an export button. Once exported, import in the new server and it will set up PHP + Apache how it was on the old server. The current configuration would not work no, as far as I"m aware. I"d ignore the SNI bit too where it says it is possible in some circumstances at the top because I"ve never had this working Is unique IP address a must for SSL? A wildcard would allow SSL on all domains yes but you"d have to configure that, enable SSL on the main domain, make sure all links on the corp website link to HTTPS rather than HTTP (quite a big job).
Firstly how would I export my Apache profile? and import it into my new site?0 -
Your support site opens on the (old?) 88.202.xxx.xxx IP address. It also works on the sub.domain. The new IP: 137.116.xxx.xxx is a shared IP as seen in your posted list accounts image, your support site cannot open on that IP by itself. Using ~username won't work on your current setup. If you've got an extra IP address on the new server, create an account with the support.subdomain.com and give it that dedicated IP and then it will be view-able at that IP address you give it. 0 -
Firstly how would I export my Apache profile?
In WebHost Manager, search for Easy with search tool to find EasyApache. Depending on which you're using, 3 or 4, the documentation for both can be found here: EasyApache Profile Stage - EasyApache - cPanel Documentation EasyApache 4 - Create a Profile - EasyApache 4 - cPanel Documentation0 -
I am working on getting a second IP in for the sub domain, how would I transfer a apache 3 profile into a apache 4 As the live site uses 3, and there is only a option for 4 on the new site please see picture below 0 -
43552 New site 0 -
Old website 0 -
how would I transfer a apache 3 profile into a apache 4
I don't think that's possible. You might consider going back to 3: How to Install or Uninstall EasyApache 4 - EasyApache 4 - cPanel Documentation0 -
This system never had EasyApache 3. Reverting is not possible. This is the error I am getting 0 -
See if this thread is helpful: EasyApache4 revert to EasyApache3 on freshinstall (whm 58) 0 -
43582 My Apache isn't working 0 -
More details please. 0 -
Basically there is no option on the WHM control panel for apache 3 I can't upload the profile. The httpd service isn't working, so any website that was working isn't anymore The whole build is not working [root@vps4 home]# service httpd start Redirecting to /bin/systemctl start httpd.service Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. [root@vps4 home]# /etc/init.d/httpd start -bash: /etc/init.d/httpd: No such file or directory [root@vps4 home]# Message from syslogd@vps4 at Nov 24 10:47:58 ... kernel:Restarting system. The service "httpd" appears to be down. Server vps4.example.com Primary IP Address 10.1.2.4 Service Name httpd Service Status failed Notification The service "httpd" appears to be down. Service Check Method The system failed to connect to this service"s TCP/IP port. Reason Unable to connect to port 80 on 127.0.0.1: Connection refused: Died Number of Restart Attempts 1 Startup Log Nov 24 10:48:32 vps4.example.com systemd[1]: Starting Apache webserver managed by cPanel EasyApache... Nov 24 10:48:32 vps4.example.com restartsrv_httpd[737]: (XID phf787) The system could not find the "httpd" binary. Nov 24 10:48:32 vps4.example.com systemd[1]: httpd.service: control process exited, code=exited status=2 Nov 24 10:48:32 vps4.example.com systemd[1]: Failed to start Apache webserver managed by cPanel EasyApache. Nov 24 10:48:32 vps4.example.com systemd[1]: Unit httpd.service entered failed state. Nov 24 10:48:32 vps4.example.com systemd[1]: httpd.service failed. Memory Information Used 693 MB Available 26.8 GB Installed 27.48 GB Load Information 0.00 0.08 0.05 Uptime 6 minutes IOStat Information avg-cpu: %user %nice %system %iowait %steal %idle 0.44 0.02 0.28 0.06 0.00 99.20 Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn sdb 1.31 9.47 0.30 3405 108 sda 28.14 1348.93 79.28 485237 28517 Top Processes PID Owner CPU % Memory % Command 1835 root 16.13 0.05 /usr/local/cpanel/scripts/restartsrv_proftpd --check --notconfigured-ok 1757 root 4.55 0.34 spamd child 1429 root 1.14 0.35 /usr/local/cpanel/3rdparty/perl/522/bin/perl -T -w /usr/local/cpanel/3rdparty/bin/spamd --max-spare=1 --max-children=3 --allowed-ips=127.0.0.1,::1 --pidfile=/var/run/spamd.pid --listen=5 --listen=6 1 root 0.70 0.03 /usr/lib/systemd/systemd --switched-root --system --deserialize 21 1746 root 0.59 0.11 tailwatchd - chkservd - ftpd check The chkservd process attempts to connect to "127.0.0.1:80" in order to validate that this service is functioning. If you blocked connections with iptables or the "Host Access Control" interface in WHM, this failure may be a false positive. To resolve this issue, either open the firewall to allow connections as the root user to "127.0.0.1:80" or disable checks for this service in WHM"s "Service Manager" interface with the "Configure Monitor Settings" link below. Configure Monitor Settings:0 -
Did you see the 3rd post in that thread I linked you to, suggesting you manually open the URL? Update. After switching on the ea3 whm menu does not appear. solution. ipadress:2087/yourcpsession12345678/cgi/easyapache.pl then make php compilation process in the whm menu will appear after completion. I missed you ea3. ;)
0 -
I did see that thread, however nothing would start after trying to revert to EasyApache 3 Would it be a idea to burn the box and install a version of CPanel that has Easy three preinstalled? 0 -
EasyApache4 is now the default I believe. What happened when you manually pasted the last part of that URL and opened the page in your browser? cgi/easyapache.pl 0 -
Either that or manually apply the setting, by reading the old profile 0 -
I have managed to upload the profile But the Apache service is restarting?? 0 -
I think I'd have rebuilt Apache first, and then uploaded the profile and built Apache once again afterward. Or is that what you did here? More details are always helpful. 0 -
I did the following commands mkdir /usr/local/apache.ea3/ Then /scripts/migrate_ea3_to_ea4 --revert --run Then tried the extension uploaded the profile and tried to restart the httpd service with no success 0 -
I am getting the following error redirecting to /sbin/systemctl start httpd.service job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -em' for details 0 -
Are you able to get to the EasyApache3 page? 0
Please sign in to leave a comment.
Comments
65 comments