1
24.1 Legacy Series / Re: Frustrating failure with simple port forwading
« on: March 29, 2024, 04:02:28 pm »
Looks like it was already off, then. Problem fixed. Thank you!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
24.1 Legacy Series / Re: Frustrating failure with simple port forwading
« on: March 29, 2024, 03:47:42 pm »
I couldn't even find a setting for HTTP->HTTPS redirection to disable, but changing the OPNSense UI port seems to have worked. I can now reach the page with these rules. Thank you!
3
24.1 Legacy Series / Frustrating failure with simple port forwading
« on: March 29, 2024, 03:42:36 am »
I'm having a problem with OPNSense that's driving me crazy. I just want to forward a port. I've got OPNSense running on a Proxmox VM serving as my gateway (192.168.1.1/16), and Ubuntu in an LXC container running an nginx docker image that i want to use as reverse proxy. I just want to port forward from OPNSense's public IP on port 80/443 to reach the NGINX webpage (192.168.1.13:81) to start with. I can reach said webpage no problem without NAT.
Using examples I followed on youtube videos, I created following following NAT port forwarding rules:
Source:Interface(WAN), Protocol(TCP), address(*), ports(*)
Destination: Address(WAN address), port(80)
NAT: IP(192.168.1.13), Ports(81)
(and a duplicate one for Destination port(443))
As I said, it's easy to verify the port is open with simple online tools, but when I try OPNSense public IP address, it goes nowhere. Without these rules, the public IP address for OPNSense takes me to the login page, as expected. I turned off all the firewalls I could find in proxmox for the VM, the container, the node and the datacenter in case it was messing it up, but that didn't help.
Frustrated with that, I tried to simply port forward to my old tp-link router that is now just serving as a wireless access point and try to reach the admin page. Modifying the previous rules, to simply change the NAT IP to 192.168.1.3, but those completely fail to NAT as well.
This is probably a simple problem but i'd appreciate any help. Thanks.
Using examples I followed on youtube videos, I created following following NAT port forwarding rules:
Source:Interface(WAN), Protocol(TCP), address(*), ports(*)
Destination: Address(WAN address), port(80)
NAT: IP(192.168.1.13), Ports(81)
(and a duplicate one for Destination port(443))
As I said, it's easy to verify the port is open with simple online tools, but when I try OPNSense public IP address, it goes nowhere. Without these rules, the public IP address for OPNSense takes me to the login page, as expected. I turned off all the firewalls I could find in proxmox for the VM, the container, the node and the datacenter in case it was messing it up, but that didn't help.
Frustrated with that, I tried to simply port forward to my old tp-link router that is now just serving as a wireless access point and try to reach the admin page. Modifying the previous rules, to simply change the NAT IP to 192.168.1.3, but those completely fail to NAT as well.
This is probably a simple problem but i'd appreciate any help. Thanks.
Pages: [1]