We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
please help... i'm stuck. NAT --> 80/443
-
- Posts: 4
- Joined: Sun Sep 22, 2019 9:03 am
- Os: CentOS 6x
- Web: apache + nginx
please help... i'm stuck. NAT --> 80/443
Hi all,
New user to vestacp. I already have my mail running but for some reason WWW doesnt work.
Here is my situation:
I have a pfsense router/gateway i forwarded port 80,443 tcp to 10.0.250.133 <-- internal ipadres.
Mail already done and works.
But when i login on other SSH servers port 443 and port 80 are closed.
What am i doing wrong?
What i have done so far:
goto IP and reread IP.
i have there: 10.0.250.133 --> externalip.
Status shared. (owner admin users admin.
templates: apache on default and nginx on hosting.
checked for SElinux (is disabled)
I have stopped iptables flushed the tables disabled the iptables but no go.
What am i doing wrong?
what i found is when i NMAP localhost theres no port 80,443 also no 8080 and 8443
When i do NMAP on 10.0.250.133 there is a port 80,443 and 8080, 8443
I have a already running webserver on 10.0.250.134 and thats works great so i dont have any rush to get this to work.
(my situation is all the servers are Virtual machines running on vmware esxi 6.5).
I'm out of options so i hope someone can point me to the right direction :).
Regards,
Tim
New user to vestacp. I already have my mail running but for some reason WWW doesnt work.
Here is my situation:
I have a pfsense router/gateway i forwarded port 80,443 tcp to 10.0.250.133 <-- internal ipadres.
Mail already done and works.
But when i login on other SSH servers port 443 and port 80 are closed.
What am i doing wrong?
What i have done so far:
goto IP and reread IP.
i have there: 10.0.250.133 --> externalip.
Status shared. (owner admin users admin.
templates: apache on default and nginx on hosting.
checked for SElinux (is disabled)
I have stopped iptables flushed the tables disabled the iptables but no go.
What am i doing wrong?
what i found is when i NMAP localhost theres no port 80,443 also no 8080 and 8443
When i do NMAP on 10.0.250.133 there is a port 80,443 and 8080, 8443
I have a already running webserver on 10.0.250.134 and thats works great so i dont have any rush to get this to work.
(my situation is all the servers are Virtual machines running on vmware esxi 6.5).
I'm out of options so i hope someone can point me to the right direction :).
Regards,
Tim
-
- Posts: 4
- Joined: Sun Sep 22, 2019 9:03 am
- Os: CentOS 6x
- Web: apache + nginx
Re: please help... i'm stuck. NAT --> 80/443
For now this is what i have done:
Changed all the ports in httpd/ngnix.conf to 80 and 443 (ip deleted so it looks on all ip's.)
No go.....
Change the IP in vesta:
11 Sep 2019
10.0.250.133 → 82.xx.xx.xx domain.nl
255.255.255.0
Domains:5
Owner:admin
ens192
Status:shared
Users:admin
I removed the extern ip and saved. Then on all the domains i see not my external ip but 10.0.250.133
Far as i see this should work but....no go...
I just dont get it.. I telnet to 10.0.250.133 80 and 443 and ports are open. But when i forward it 80 and 443 is closed or no even available.
When i forward it to my other webserver no issues...
Well still searching.. but it seems to be a bug in vesta/apache/ngnix something must be wrong there.
regards,
Tim.
Changed all the ports in httpd/ngnix.conf to 80 and 443 (ip deleted so it looks on all ip's.)
No go.....
Change the IP in vesta:
11 Sep 2019
10.0.250.133 → 82.xx.xx.xx domain.nl
255.255.255.0
Domains:5
Owner:admin
ens192
Status:shared
Users:admin
I removed the extern ip and saved. Then on all the domains i see not my external ip but 10.0.250.133
Far as i see this should work but....no go...
I just dont get it.. I telnet to 10.0.250.133 80 and 443 and ports are open. But when i forward it 80 and 443 is closed or no even available.
When i forward it to my other webserver no issues...
Well still searching.. but it seems to be a bug in vesta/apache/ngnix something must be wrong there.
regards,
Tim.
-
- Posts: 4
- Joined: Sun Sep 22, 2019 9:03 am
- Os: CentOS 6x
- Web: apache + nginx
Re: please help... i'm stuck. NAT --> 80/443
Yes bug discovered. Trying to get the bug back with new server situation before confirm its a bug :)
To be continued.
To be continued.