Messages

1

24.1 Legacy Series / Re: Wireguard VLAN no longer gets an internet connection after update

« on: January 20, 2024, 12:13:17 pm »

I think I found the problem, somehow the vpn gateway group got deleted but the rules still reference it.
I recreated the group and everything is working fine again.

2

24.1 Legacy Series / Re: Wireguard VLAN no longer gets an internet connection after update

« on: January 20, 2024, 11:47:13 am »

Here you go, it shows working as before

3

24.1 Legacy Series / Wireguard VLAN no longer gets an internet connection after update

« on: January 19, 2024, 10:43:17 pm »

After updating to the development build and from there to the release candidate my wireguard vlan is no longer getting an internet connection. I have no idea why this is, but I saw that osfirewall and os-wireguard show as missing under plugins and this can't be resolved.

4

23.1 Legacy Series / Re: NUT (UPS) daemon is unable to start after upgrade

« on: January 27, 2023, 11:39:46 am »

Ok, strange thing. I used the cat command and realized that the script hasn't been changed to reflect the changes to nut:nut. So I applied the patch a third time and now it just works as intended. No idea why it didn't work before but it seems to be working just fine now, even after a reboot.

5

23.1 Legacy Series / Re: NUT (UPS) daemon is unable to start after upgrade

« on: January 27, 2023, 11:11:46 am »

Code: [Select]

root@OPNsense:/var/db # /usr/local/etc/rc.d/nut restart
nut not running? (check /var/db/nut/upsd.pid).
Network UPS Tools - UPS driver controller 2.8.0
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Can't chdir to /var/db/nut: Permission denied
Driver failed to start (exit status=1)
/usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Exact same as above

Code: [Select]

root@OPNsense:/var/db # ls -la nut/
total 19
drwxr-x---   2 uucp  uucp    6 Jan 19 04:44 .
drwxr-xr-x  23 root  wheel  34 Jan 27 10:23 ..
-rw-r--r--   1 nut   nut     6 Jan 18 10:00 upsd.pid
-rw-r--r--   1 nut   nut     6 Jan 27 10:23 upsmon.pid
srw-rw----   1 nut   nut     0 Jan 18 10:00 usbhid-ups-ups
-rw-r--r--   1 nut   nut     6 Jan 18 10:00 usbhid-ups-ups.pid

6

23.1 Legacy Series / Re: NUT (UPS) daemon is unable to start after upgrade

« on: January 27, 2023, 10:25:47 am »

Does this do the job? https://github.com/opnsense/plugins/commit/16cbe99ebf
# opnsense-patch -c plugins 16cbe99ebf

Unfortunately it doesn't change anything for me

7

23.1 Legacy Series / Re: 23.1r1 - version displayed in UI?

« on: January 13, 2023, 07:29:17 pm »

I've got the same problem when trying to upgrade from the community repository.

8

Tutorials and FAQs / Re: Tutorial 2022/02: HAProxy + Let's Encrypt Wildcard Certificates + 100% A+ Rating

« on: March 18, 2022, 08:52:27 pm »

For temporary fix, edit the VIP, save without any changes, then apply.

Thank you this actually works for now, I hope there will be a proper solution or fix for this soon though

9

Tutorials and FAQs / Re: Tutorial 2022/02: HAProxy + Let's Encrypt Wildcard Certificates + 100% A+ Rating

« on: March 18, 2022, 03:10:11 pm »

I have a very serious problem with this haproxy config since I updated to 22.1.3. Suddenly haproxy didn't start anymore. On further investigation trying to start haproxy through the commandline showed that suddenly the ipadresses for the frontend cannot be bound anymore:

Code: [Select]

root@OPNsense:/home/David # /usr/local/etc/rc.d/haproxy start
Starting haproxy.
[ALERT]    (21351) : Starting frontend 1_HTTP_frontend: cannot bind socket (Can't assign requested address) [192.168.64.1:80]
[ALERT]    (21351) : Starting frontend 1_HTTPS_frontend: cannot bind socket (Can't assign requested address) [192.168.64.1:443]
[ALERT]    (21351) : [/usr/local/sbin/haproxy.main()] Some protocols failed to start their listeners! Exiting.
/usr/local/etc/rc.d/haproxy: WARNING: failed to start haproxy
Any help on how to fix this would be really appreciated

10

22.1 Legacy Series / Re: OPNsense 22.1.2 upgrade error

« on: March 01, 2022, 06:07:00 pm »

Same here. I did a complete reinstall and update and rebootet from the backup config afterwards but now I have the same error for the acme and ddclient packages

Edit: The cloudflare mirror seems to be the issue, with the default mirror it worked just fine

11

22.1 Legacy Series / Re: os-ddclient

« on: January 21, 2022, 10:12:48 am »

Yes, a few infos about the development plans of ddclient would be very welcome, I also rely on cloudflare implementation and in the current client the wildcart box seems not to be doing anything

12

General Discussion / Re: Dynamic DNS Wildcart with cloudflare not working

« on: January 17, 2022, 08:47:07 pm »

bump

13

General Discussion / Re: Dynamic DNS Wildcart with cloudflare not working

« on: January 12, 2022, 07:37:33 pm »

bump

14

General Discussion / Dynamic DNS Wildcart with cloudflare not working

« on: January 10, 2022, 02:47:09 pm »

Hi,
as described in the title I have the problem that the Dynamic DNS service doesn't update all my subdomains in cloudflare even though I selected Wildcart and created a corresponding cname record on the website. Only example.com is updated, not subdomain.example.com.
I hope someone can help me getting it running correctly.

15

German - Deutsch / Re: Mullvad Wireguard keine Verbindung

« on: December 19, 2021, 02:36:23 am »

Danke das wars, auf der Website stehen nur noch die sock5 Adressen. Da wäre ich im Leben nicht drauf gekommen.