Quote from: drgeoff on May 13, 2024, 03:31:07 PMQuote from: NOBi on May 13, 2024, 12:47:34 PMExact same problem came up on mine.
No idea what changed as this worked before without issue.
Fix was enabling AccessFromWAN...
System Management/Device Admin/AccessFromWAN/Port:=checked
To be safe, change Port and Webpage Admin Password (in dashboard) since access from internet is now open.
System Management/Device Admin/Web Server/Port
1. Disabled is the default and will be applied if the OBi202 is reset.
2. Setting it to enabled using the setting above requires connecting the PC to the 202's LAN port and rebooting the PC. The method I pointed to in my post is easier. Just a few key presses on the phone.
3. "since access from internet is now open." is unnecessarily frightening. It is very rare for the 202 to have a public IP address. There is invariably another NAT router between the public internet and the 202 and that would need to have been deliberately configured to forward port 80 to the 202.
As I previously stated, I also lost access to the internal web server, whereas previously accessed it through the LAN IP address.
Setting the AccessFromWAN to enabled, gave me back the internal web server accessed through the LAN IP address just as before, no recabling required.
Does this make sense -- no, but it worked for me, while nothing else I tried got the web server back.
Something funky is going on with these devices as EOL is now here, and undocumented updates are sent to our devices disabling various services. I wouldn't be surprised if attempts are being made to disable local web access prior to shutting down OBiTalk, but I really hope that is not the case. For now, this workaround works.