HTTP 500 Error

[Ian Daniels]

As I believe it to be a problem with the SSL

Basically in a previous thread the main test website wasn't working when entering the public IP in the URL, we have since discovered that amending the local host file on my laptop and using the FQDN it worked

I have tried to do this in my host file for this website I am having issues with and getting the http error 500 problem

I have tried to insert the public IP address and not use FQDN and I am getting the original problem I had with my first site

If that makes sense

 

[Infopro]

in the external DNS I have three entries

What external DNS are you speaking of?

 

[Ian Daniels]

AWS and Zerigo and cloud flare

 

[Ian Daniels]

The site I am trying to move is - Removed -

I have got the - Removed - working

 

[Infopro]

AWS and Zerigo and cloud flare

You're going to have to go over your settings, or disable cloudflare until you get things moved and sorted.

 

[Ian Daniels]

the support is ssl so it is https access

cloud flare shouldn't matter if I am changing my local host file while I test it?

 

[Infopro]

Well, it's not working, whatever you're doing, right?

I have removed both links, no need here. But they do both work for me. I assume this is expected as they're on the old server still correct?

 

[Ian Daniels]

Yes it is pointing to the old server

Now if you was to use the following IP you will see the problem

137.116.xxx.xxx

This is the new/test site

to access the main mpp site you have to edit your local host file

 

[Infopro]

Is that the shared IP for the server?

 

[Ian Daniels]

I have just found a entry in a log don't know if it is relevant

[23-Nov-2016 10:05:56 UTC] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 196608 bytes) in /home/******/public_html/wp-content/plugins/s2member/includes/classes/constants.inc.php on line 2201

Yes, that is the IP it will be using

 

[Infopro]

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.

New I have just found a entry in a log don't know if it is relevant

It's not.

 

[Ian Daniels]

The IP address is assigned

 

[Ian Daniels]

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 IP

 

[Infopro]

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.

 

[Ian Daniels]

So if??? I change the external IP addresses from the live site to the new site the new site should work?

 

[Ian Daniels]

Is this what you are talking about

 

[Infopro]

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.

 

[Infopro]

Is this what you are talking about

Yes.

 

[Ian Daniels]

Thank you

 

[Ian Daniels]

The support sub domain is not covered by cloud flare that is why it has a ssl cert installed