SSL certification successful but website and vps virtualmin panel is not responding right after

Help
22

[root@vps ~]# ls -l /etc/httpd/

total 4
drwxr-xr-x 2 root root   37 Dec 25 18:16 conf
drwxr-xr-x 2 root root  152 Dec 25 18:16 conf.d
drwxr-xr-x 2 root root 4096 Dec 13 15:46 conf.modules.d
lrwxrwxrwx 1 root root   19 Oct 18 16:00 logs -> ../../var/log/httpd
lrwxrwxrwx 1 root root   29 Oct 18 16:00 modules -> ../../usr/lib64/httpd/modules
lrwxrwxrwx 1 root root   10 Oct 18 16:00 run -> /run/httpd
lrwxrwxrwx 1 root root   19 Oct 18 16:00 state -> ../../var/lib/httpd
23

[root@vps ~]# ls -l /etc/httpd/conf/

total 16
-rw-r--r-- 1 root root     0 Dec 25 18:16 httpd.conf
-rw-r--r-- 1 root root 13064 Oct 18 16:00 magic
24

Versus

Two different webservers listening, isn't that weird?

3 Likes
25

Well that is bad.
Do you have any kind of backup?

3 Likes
26

Yes I have backup of the files

1 Like
27

Restore that file to the last one you have.
And then restart the service.

3 Likes
28

I dont have the backup of the httpd.config file just the public_html dir

29

Well then...
You may have to reinstall VirtualMin.

Do you have a previous "snapshot" of the server?

3 Likes
30

So we had this website on a business hosting plan, and then we had to add a feature with websockets so we tried vps hosting. Now after setting up the vps server with Apache and replacing the dns records with the new vps ip address it was working on insecure http. After I resolved the ssl issue by replacing the ipv6 address as the new IP address the ssl generation was successful however after some time the virtualmin and everything crashed. Now the thing is the old ip address when accessed directly was also showing forbidden for some reason. Now i replaced all the vps ip address with the old business hosting ip address and now it is working fine but it is showing the business hosting files. And here we are stuck as to what to do next with the vps hosting because if i try setting up again similar problem might arise again

31

Sounds like a Virtualmin problem and not so much a certificate specific issue?

4 Likes
32

Now the thing is, at one point the old ip was working fine, even with SSL; and the NEW_IP with VPS (only http) was working fine. Not sure if webserver config files were empty or not at that moment. As soon as SSL started working for New_IP; both New and Old crashed, and surprisingly old started showing 403 error. And here we are stuck as to what to do next with the vps hosting because if we try setting up VPS again, even old business hosting might shut down again.
Can some DNS record might be causing some conflicts?

33

Why would SSL or virtualmin on VPS (different IP address) cause Business Hosting plan show forbidden error?

34

If this is an important business resource, you really need to hire someone who has a solid understanding of DNS and hosting.

4 Likes
35

Thx everyone, we were able to sort this issue. We simply put vps server's ip address in dns records of domain registrar, and followed the process for SSL cert creation. And it worked like a charm.

Thx everyone for your help!!

1 Like
36

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.