Issues when transfering servers

Help
42

let me reboot now.

I haven't, but when I ran:
sudo service iptables save
it gave me:
iptables: unrecognized service

these commands worked fine:

root@lenovo-server:/etc/apache2/sites-available# sudo iptables -A INPUT -p tcp --dport 443 -j ACCEPT
root@lenovo-server:/etc/apache2/sites-available# sudo iptables -A INPUT -p tcp --dport 80 -j ACCEPT

43

root@lenovo-server:/etc/apache2/sites-available# ufw status

Status: inactive

so the firewall isn't even on.

44

rebooting now.

45

iptables --list

I suspect that if you have both a drop and an accept, the drop might come first.

2 Likes
46

Just for clarity: ufw and iptables are both firewalls
[but not the SAME firewall]

sudo apt-get install ufw
sudo apt-get install iptables

2 Likes
47

ah ok. Yeah so UFW isn't enabled. Iptables --list returned this:

george@lenovo-server:~$ sudo su
[sudo] password for george:
root@lenovo-server:/home/george# iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

48

Looks like my iptables rules for 80 and 443 didn't take effect.

49

hmm...
So, what is blocking/stopping the HTTPS requests?

Let's recheck the port forwarding.

2 Likes
50

80 and 443 port forwarded to internal server ip with TCP. Triple checked.

Maybe router NAT filtering, or misconfigured apache2.conf?

51

Four eyes are better than two.
Can I see?

What shows?:
netstat -pant | grep -i listen | grep apache

2 Likes
52

SO WEIRD

root@lenovo-server:/home/george# netstat -pant | grep -i listen | grep apache

tcp6 0 0 :::80 :::* LISTEN 772/apache2

only port 80 is open. There has to be some firewall rule disabling port 443, or apache2.conf is not set to use it.

Screen Shot 2022-08-29 at 11.08.29 PM
Screen Shot 2022-08-29 at 11.08.29 PM940×84 9.38 KB

Screen Shot 2022-08-29 at 11.08.41 PM
Screen Shot 2022-08-29 at 11.08.41 PM940×201 12.7 KB

Screen Shot 2022-08-29 at 11.08.58 PM
Screen Shot 2022-08-29 at 11.08.58 PM903×59 7.83 KB

53

443 isn't listening.

Show:
apachectl -t -D DUMP_VHOSTS

2 Likes
54 
root@lenovo-server:/etc/apache2# apachectl -t -D DUMP_VHOSTS
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
VirtualHost configuration:
*:80                   is a NameVirtualHost
         default server www.techmasterdesign.com (/etc/apache2/sites-enabled/000-default.conf:1)
         port 80 namevhost www.techmasterdesign.com (/etc/apache2/sites-enabled/000-default.conf:1)
                 alias techmasterdesign.com
         port 80 namevhost groupfinder.cc (/etc/apache2/sites-enabled/groupfinder.conf:1)
                 alias www.groupfinder.cc
         port 80 namevhost wavebuddha.com (/etc/apache2/sites-enabled/wavebuddha.conf:1)
                 alias www.wavebuddha.com
55

That shows it only listening on port 80.

Did you a2ensite?
show:
ls -l /etc/apache2/sites-enabled/

2 Likes
56

I did

lrwxrwxrwx 1 root root 35 Aug 29 20:40 **000-default.conf** -> **../sites-available/000-default.conf**

lrwxrwxrwx 1 root root 42 Aug 29 22:36 **000-default-le-ssl.conf** -> **../sites-available/000-default-le-ssl.conf**

lrwxrwxrwx 1 root root 35 Aug 29 21:10 **groupfinder.conf** -> **../sites-available/groupfinder.conf**

lrwxrwxrwx 1 root root 34 Aug 29 21:10 **wavebuddha.conf** -> **../sites-available/wavebuddha.conf**
57

Did you restart apache?

Show:
ls -l /etc/apache2/sites-available/

2 Likes
58

the whole server and apache yeah lol

59

maybe i didn't enable ssl module in apache: ()

3 Likes
60

show:
ls -l /etc/apache2/sites-available/

2 Likes
61

Maybe you need to remove the IF wrapper:

2 Likes