IPSec did pop back up with an nginx error but removed it again and just waited a couple hours longer. I removed every widget (as I saw there were multiple widgets along with IPSec that was being logged), rebooted, waited it out for a couple minutes, and slowly re added widgets. I tried updating to the 2.3.1 snapshot and problem persisted. I had this problem (not exactly but same effect). Installed package was Backup/Restore only. WAN is PPPoE on re0_vlan7, LAN and other OPT interfaces are re1_vlan10 / 20 / 30 / 40 / 50 / 60. Reverting back to HTTP didn't help either, I still get redirected to HTTPS, even after a reboot. ![]() When I had console access via serial I tried to restart the webConfigurator and rebooted the device. I can, however, ssh via an OPT interface - but HTTPS doesn't work there as well. Well, now, nearly 10h after working flawlessly the second device goes down as well. To get to production again I installed my config.xml to a different APU1 which I just updated to 2.3 from 2.3RC. Doesn't route also but still hands out DHCP leases to clients. Today the unit wasn't accessible via HTTPS (504 Gateway Time-out). ![]() Updated an APU1 yesterday afternoon from 2.2.6 to 2.3 with Nano install on an SD card. I have quite strange a phenomena and don't know exactly where to start troubleshooting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |