SSL and Redirecting to virtual domains

grandm1961

Verified User
Joined
Nov 30, 2020
Messages
34
Hello, I have a weird problem, I updated my DirectAdmin and my server and all the SSL certificates and that all seem to go well.
But now I have this issue that if I check a virtual domain I get this message webserver is functioning normally instead of the template.
Also I have the virtual domains redirected to HTTPS and that don't work either it gives the wrong SSL of my server.
I double checked everything and I'm lost here, since it always worked but now it doesn't work for no domain excepts for the DA Panel. Templates are not shown only the message webserver is functioning normally. How can I fix this?
 
I think you have to give us at least 1 virtual domain to be able to check what is going wrong.

Also tell us which way you have the domains redirected to https, via DA itself or via a .htaccess file?

It sounds a bit like DNS issue, because if you get the message "the webserver is functioning normally" then it's pointed to the ip, but the server itself does not redirect to the appropriate domain.
So have you doublechecked DNS and the domain ip's, nameserver and namesever ip's? Because that could also be a valid reason that wrong SSL's are displayed and you are pointed to the server landing page now.
 
My domain is duraweb.eu and other domains are schootenvan.nl and bloomlife.nl and doorpakkers.eu all are redirected in DA in the SSL certificate to redirect to HTTPS. the domain ip's are all the same and I have the dns from Cloudflare which are also all the same. I have used the same settings now for 2 years and haven't changed anything at all.
 
It looks allright externally, which makes my suspicion stronger that it's local DNS resolving having an issue.
Is bind/named running on the server?
Can you check the logfiles for errors, because it seems al the domains are having the same issue.
Also check your /etc/resolv.conf to be sure and check that in /etc/hosts the 127.0.0.1 is pointing to localhost and not server.domain.com or something likethat.

But I guess from the logs you should be able to find what is going wrong.
 
Named is running, hosts file 127.0.0.1 is pointing to localhost and the resolve.conf is pointing to KPN on which I run the server from to 2 ip addresses. now I have to go through all the logfiles or can you give me a specific one to look for?
 
and the resolve.conf is pointing to KPN
Could you temporarily try to put the first line in the resolv.conf to 127.0.0.1 and then restart bind, see if that makes any difference? You can remove it again if it does not change anything. It's just to test and see.

As for logfiles, yes there are many. I would start with the named logs, which (if not changed) are in /var/log/messages in RH alike systlems.
You could do a tail of the log, call one site and refresh it a couple of times and see what happens.

Same for /var/log/httpd/access_log and /var/log/httpd/domains/domain.nl.log and error.log also.

So I would start with those logfiles and see if you can find anything odd.
 
changing resolve doesn't do anything it keeps giving me the message webserver is running normally
And so fa I can't find anything abnormal than except the ID which I seen that on the forums is nothing than a warning
 
Fixed it, it seemed that the https.conf of all the domains were wrong for the internal IP address , The router has changed the IP address for the server and I have changed it all in the HTTPD.CONF to the proper one. Thnx for your help, all seems fine now
 
Ah great you found it. As said, dns related, so yes if the ip is not correct anymore... Glad to see it fixed.

Suggestion: I didn't know this was a LAN situation. You might want to consider to either configure a static ip for your server, or maybe better, reserve the ip address for your server in DHCP then this issue can't happen again for whatever reason.
Except in case of a full router reset which makes the router loose dhcp reservations.
 
Strange thing do, since it has been for at least a 6 months like the wrong ip and always worked except today. So why it happend now I don’t know, at least one more way to mark down as a solution. And i am using this ip in the router a long time, so next time i swap a provider something i need to be aware of.

Thnx for the help anyway.
 
since it has been for at least a 6 months like the wrong ip and always worked except today.
Hmmz... that's very odd indeed.
Well at least you have another thing you can keep in mind to check if things start to do odd again.

As for the help, you're welcome ofcourse. That's were the forum is for.
 
Back
Top