After nameserver update, constant Http 500 error


#1

Hello,
I’m using A2hosting hosting, and I changed my nameserver to the ones generated by Cloudflare. Well I think the website won’t have any downtime, but since then, my website is down. My website is www.csgoshopsmurf.com . Can you please help me with that?
DNS are updated from GoDaddy.


#2

When you set up your account and domain here, it should have scanned your DNS records. Is that 68.66 IP address the one that was automatically scanned? Or did you enter it yourself? Your website isn’t responding on that IP address.

For now, double-check that IP address by comparing it with what’s in A2hosting’s DNS listing for your website.


#3

Hi @raman19930, I can see that your real a2hosting IP is being used, rather than the CloudFlare proxy pair & that although the website http://www.csgoshopsmurf.com/ when visited, redirects to https://csgoshopsmurf.com/ and that then times-out with a 500 Internal Server Error.

I suggest that the problem is with your webserver/service, and not your CloudFlare implementation.

I tested using telnet to the HTTP site like this (enter twice, after the host: line): -

% telnet 68.66.216.18 80
Trying 68.66.216.18...
Connected to 68.66.216.18.
Escape character is '^]'.
GET / HTTP/1.1
host:www.csgoshopsmurf.com

HTTP/1.1 301 Moved Permanently
Location: https://csgoshopsmurf.com/

I tested the HTTPS site like this (enter twice, after the host: line): -

% openssl s_client -connect csgoshopsmurf.com:443 -crlf**
CONNECTED(00000003)
Boring SSL/TLS stuff
---
GET / HTTP/1.1
host:csgoshopsmurf.com

HTTP/1.1 500 Internal Server Error

I recommend that you get a2hosting support to help you sort out your server, and then - only when it’s working - come back to your CloudFlare config.


#4

Thank you so much! The issue is fixed.

Hosting support stated that right before switching to Cloudflare I installed a plugin which caused the constant 500 error.

Neither cloudflare nor hosting had to do anything with it. It was just WordPress.


#5

Great news, @raman19930


#6

This topic was automatically closed after 14 days. New replies are no longer allowed.