Messages

Are you using HTTP or HTTPs?

If you can ssh into the device try to reset WebGUI access >
https://docs.opnsense.org/troubleshooting/webgui.html

Regards,
S.

Thank you for your suggestion, I've just had time to look into it now and it's worked perfectly :)

HTTP I believe. In the top corner it always says "not secure"

Good morning :)

I've been using Opnsense for the last month or two and in the main it's fantastic, especially coming from the closed world of router firmware :)

My problem began last night when the internet went down, all seemed well from our end but to make sure, we reset the box Opnsense was running on, all was well and it beeped to confirm it had reloaded. The internet was still down for a further 20 mins then came back up on it's own.

However, since then, I cannot access the webGUI on the standard 192.168.1.1. I get a message that This site can't be reached, took too long to respond.

Any clues as to what I can do next? Still very much green in regards to setting all this up properly. It was working perfectly for 42 plus days before the reset.

If you require any other information please ask :)

[My Working Settings:]

Just updated to 27.7.3, with latest os-ddclient 1.15, and everything is working fine with DuckDNS, right away for me (for the first time).

Thanks for the hard work on getting this up and running and stable.

I've spent a long time waiting to move from the legacy DDNS client, but could never get the os-ddclient stable and working with DuckDNS.

I had even JUST switched to a DuckDNS container on unRAID (it worked within 1 second of booting the first time)... as I upgraded to OPNsense 27.7.1... and still couldn't get os-ddclient working properly.

Decided to give it one last go with OPNsense's os-ddclient when I saw this thread, and it worked immediately, without any editing of files, or manipulating of the underlying configuration files via SSH.

So I've removed the unRAID docker with the hope that this stays solid between reboots.

My Working Settings:

General ->

Interval = 600 seconds
Backend = native

Accounts ->

Service = duckdns
Username = blank
Password = <token>
Hostnames = hostname.duckdns.org
Check ip method = Interface [IPv4]
Interface to monitor = WAN
Check ip timeout = 10
Force SSL = unchecked

Thanks again!

Perfect, thanks for the setup instructions - was scratching my head as to why I wasn't getting an IP showing on Opnsense, also I'd put a username where none was needed. Total newb here but again, thank you :)

Hi, first post :)

This is just for comparison to yours as I do not have the issue you describe.

CPU: i5-6400
SSD: Integral 256 GB Nvme
RAM: 4GB DDR4 2400
NICs: 2x Intel PRO 1000

Your machine is superior to mine in both CPU and RAM but I have an Intel Pro dual gigabit NIC. Google, Youtube etc work perfectly and I get 940mbits on my gigabit connection. A long shot but it may be your card unless someone brighter than I (i.e, everyone :D ) can shed some light.