1
General Discussion / Re: Preferred landing page not working
« on: September 15, 2024, 03:35:31 pm »
I'm happy to report that this is finally working for me with the release of 24.7.4.
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
General Discussion / Re: Preferred landing page not working
« on: September 11, 2024, 01:07:12 pm »
Thank you for taking the time to reply, JamieLaing. Unfortunately, even with this (which is what I originally thought) it still doesn't work for me.
It's a minor inconvenience, I guess I'll just live with it.
It's a minor inconvenience, I guess I'll just live with it.
3
General Discussion / Re: Trouble forwarding ONLY port 80 inbound
« on: August 22, 2024, 03:49:30 pm »
The two highlighted entries in the screen shot do show a source of 108.179.33.133 to a destination of 192.168.1.77...this is indeed from the WAN inbound passing successfully. The red entry was just to show that the firewall is working as expected and blocking other ports that are not forwarded.
I do see the rule on WAN...
IPv4 TCP * * 192.168.1.77 80 (HTTP) * *
so it would appear as though the outbound Automatic NAT for reflection is working as expected.
I do see the rule on WAN...
IPv4 TCP * * 192.168.1.77 80 (HTTP) * *
so it would appear as though the outbound Automatic NAT for reflection is working as expected.
4
General Discussion / Re: Trouble forwarding ONLY port 80 inbound
« on: August 22, 2024, 03:41:06 pm »
I created Firewall Aliases for my servers so in the firewall rules it is something more easily readable than an IP address... this was step #3 in what I documented in the original post.
I did change it to the IP address of the internal server for testing. No change. I still get the timeouts.
I did change it to the IP address of the internal server for testing. No change. I still get the timeouts.
5
General Discussion / Re: No Startup/Shutdown Notification Sound
« on: August 22, 2024, 03:38:16 pm »
I can confirm that I do not have sound on my installation either. I've checked the usual suspects. Glad to know I'm not the only one, although I never posted about this because I never thought it important.
6
General Discussion / Preferred landing page not working
« on: August 22, 2024, 03:35:50 pm »
Good day, everyone.
I'm new to OPNSense but not to networking. Something weird that might be a bug, I'm not sure.
I created a new user and added them to the admin group. I disabled root. I set the preferred landing page to "ui/core/dashboard" (without quotes) as I believe it should be according to the OPNSense documentation.
On logoff and logon the system always goes to https://192.168.1.1/logon.html and presents a "PAGE NOT FOUND" error with a link to "Go back to previous page".
I've tried with a leading "/" and without. I've tried a full URL...I've tried just "core/dashboard". Nothing seems to work.
I've tried leaving the entry blank...I still get the PAGE NOT FOUND.
Is something wrong with my installation, or could this potentially be a bug?
I started with 24.7.1, but even after an upgrade to 24.7.2 this does not work (it didn't work on 24.7.1 either).
Also, if it matters, I am using MFA with a defined "Local + Timebased OTP" server.
Thanks in advance.
I'm new to OPNSense but not to networking. Something weird that might be a bug, I'm not sure.
I created a new user and added them to the admin group. I disabled root. I set the preferred landing page to "ui/core/dashboard" (without quotes) as I believe it should be according to the OPNSense documentation.
On logoff and logon the system always goes to https://192.168.1.1/logon.html and presents a "PAGE NOT FOUND" error with a link to "Go back to previous page".
I've tried with a leading "/" and without. I've tried a full URL...I've tried just "core/dashboard". Nothing seems to work.
I've tried leaving the entry blank...I still get the PAGE NOT FOUND.
Is something wrong with my installation, or could this potentially be a bug?
I started with 24.7.1, but even after an upgrade to 24.7.2 this does not work (it didn't work on 24.7.1 either).
Also, if it matters, I am using MFA with a defined "Local + Timebased OTP" server.
Thanks in advance.
7
General Discussion / Re: Trouble forwarding ONLY port 80 inbound
« on: August 22, 2024, 03:26:50 pm »
Thank you for the response.
As far as I can tell the webUI should be on TCP port 443 only. That is the setting in System -> Settings -> Administration. I even manually entered it although it was the default. The "Protocol" button at the top has HTTPS selected as well.
I re-enabled the WAN for the Listen interface.
No change in the result, though. I still get the time out.
As far as I can tell the webUI should be on TCP port 443 only. That is the setting in System -> Settings -> Administration. I even manually entered it although it was the default. The "Protocol" button at the top has HTTPS selected as well.
I re-enabled the WAN for the Listen interface.
No change in the result, though. I still get the time out.
8
General Discussion / Trouble forwarding ONLY port 80 inbound
« on: August 22, 2024, 03:01:52 pm »
Good day everyone and thank you in advance for reading.
Yes, I have searched these forums but I haven't found a post that has a problem similar to mine. I am new to OPNSense, but have worked in computers and networking for a long time. I am migrating off of a Cisco RV340 home router to a new OPNSense implementation. I have everything working except for two items, one of which I will describe here.
The scenario is that I have several servers that I need to expose externally. I've managed to do this for all servers except one. The difference is that this all the others use non-HTTP ports (465, 587, and ports in the 30000 range). These all work. I can not, however, get port 80 to successfully forward inbound.
Here is what I have done:
1. I know the OPNSense admin web page is usually externally accessible. I have disabled this by going to System -> Settings -> Admin and I have set "Listen Interfaces" to only LAN and I have checked the "Disable web GUI redirect rule" for HTTP redirect.
2. On the firewall side I have gone to Firewall -> Settings -> Advanced and checked "reflection for port forwards" and "automatic outbound NAT for reflection".
3. I created an alias for my web server.
4. Then I went to Firewall -> NAT -> Port Forward and created a new rule with the following:
Interface - WAN
TCP/IP version - IPv4
Protocol - TCP
Source - any
Source port range - any to any
Destination - WAN Address
Destination port range - HTTP to HTTP
Redirect target - my server alias
Redirect target port - HTTP
5. I set dynamic DNS to point to my WAN interface. This is confirmed working successfully.
The results are interesting...
From the LAN - The web server is up and I can see it from the LAN without problems.
From the WAN - Access always times out. I can not access via Dynamic DNS name, nor by straight IP address. In Firewall -> Log files -> Live View I can see at least some of the packets pass correctly from the correct external address to the internal destination (screen capture attached)...yet still the web page will not display on the device trying to access it. I've tried multiple browsers including Firefox, Chrome, Edge. I've tried desktop and Android phone access. All of them time out.
Any thoughts on what else could be going on here? I'm pulling my hair out with this. It is only port 80 that have not been able to get working successfully. Someone else must be doing it...
Thank you in advance for any insight or guidance you can provide.
Yes, I have searched these forums but I haven't found a post that has a problem similar to mine. I am new to OPNSense, but have worked in computers and networking for a long time. I am migrating off of a Cisco RV340 home router to a new OPNSense implementation. I have everything working except for two items, one of which I will describe here.
The scenario is that I have several servers that I need to expose externally. I've managed to do this for all servers except one. The difference is that this all the others use non-HTTP ports (465, 587, and ports in the 30000 range). These all work. I can not, however, get port 80 to successfully forward inbound.
Here is what I have done:
1. I know the OPNSense admin web page is usually externally accessible. I have disabled this by going to System -> Settings -> Admin and I have set "Listen Interfaces" to only LAN and I have checked the "Disable web GUI redirect rule" for HTTP redirect.
2. On the firewall side I have gone to Firewall -> Settings -> Advanced and checked "reflection for port forwards" and "automatic outbound NAT for reflection".
3. I created an alias for my web server.
4. Then I went to Firewall -> NAT -> Port Forward and created a new rule with the following:
Interface - WAN
TCP/IP version - IPv4
Protocol - TCP
Source - any
Source port range - any to any
Destination - WAN Address
Destination port range - HTTP to HTTP
Redirect target - my server alias
Redirect target port - HTTP
5. I set dynamic DNS to point to my WAN interface. This is confirmed working successfully.
The results are interesting...
From the LAN - The web server is up and I can see it from the LAN without problems.
From the WAN - Access always times out. I can not access via Dynamic DNS name, nor by straight IP address. In Firewall -> Log files -> Live View I can see at least some of the packets pass correctly from the correct external address to the internal destination (screen capture attached)...yet still the web page will not display on the device trying to access it. I've tried multiple browsers including Firefox, Chrome, Edge. I've tried desktop and Android phone access. All of them time out.
Any thoughts on what else could be going on here? I'm pulling my hair out with this. It is only port 80 that have not been able to get working successfully. Someone else must be doing it...
Thank you in advance for any insight or guidance you can provide.
Pages: [1]