After upgrade to FreedomBox 26.4 - can not login to Deluge

1

Hello All,

After the latest FB upgrade I can no longer login to Deluge. The url for FB Deluge login I have pasted below, all so the message from it web page.

The url below as oidc mentioned in it. Is this the issue that stopping me from login to Deluge ?

Regards: peter

https://freedombox-home.local/freedombox/apache/discover-idp/?target_link_uri=https%3A%2F%2Ffreedombox-home.local%2Fdeluge&method=get&oidc_callback=https%3A%2F%2Ffreedombox-home.local%2Fapache%2Foidc%2Fcallback&x_csrf=RBBZuvLbY4g

Massage from the url above:

Accessed using unknown domain freedombox-home.local. Please add the domain to list of configured domains.

2

Looking into this I notice that my FreedomBox does not resolve as freedombox.local today. Recently, it did, and today it does not.

Can you try using deluge using ‘home’ instead of ‘home.local’ and see if this makes any difference?

Further, I see that I can dig freedombox.local and get results (external IP, internal IP, openVPN IP) as an A record from FreedomBox, but when I try to ping freedombox.local it will not resolve.

dig freedombox.local
; <<>> DiG 9.20.18-1~deb13u1-Debian <<>> freedombox.local
;; global options: +cmd
;; Got answer:
;; WARNING: .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17016
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;freedombox.local. IN A

;; ANSWER SECTION:
freedombox.local. 0 IN A …
freedombox.local. 0 IN A …
freedombox.local. 0 IN A 10.84.0.1

;; Query time: 23 msec
;; SERVER: 192.168.XXX.YYY#53(192.168.XXX.YYY) (UDP)
;; WHEN: Sat Mar 07 10:22:15 CST 2026
;; MSG SIZE rcvd: 91

$time ping freedombox.local
ping: freedombox.local: Name or service not known

real 0m15.017s
user 0m0.003s
sys 0m0.000s

3

Hi @joseph

When I use dig freedombox-home.local I get No ANSWER SECTION: When I ping freedombox-home.local all OK it give a return.

Regards: peter

dig freedombox-home.local

; <<>> DiG 9.20.18-1~deb13u1-Debian <<>> freedombox-home.local
;; global options: +cmd
;; Got answer:
;; WARNING: .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31800
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;freedombox-home.local.		IN	A

;; AUTHORITY SECTION:
.			3416	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026030701 1800 900 604800 86400

;; Query time: 55 msec
;; SERVER: 10.64.0.1#53(10.64.0.1) (UDP)
;; WHEN: Sat Mar 07 18:01:55 GMT 2026
;; MSG SIZE  rcvd: 125

ping freedombox-home.local

PING freedombox-home.local (192.168.1.114) 56(84) bytes of data.
64 bytes from 192.168.1.114: icmp_seq=1 ttl=64 time=2.30 ms
64 bytes from 192.168.1.114: icmp_seq=2 ttl=64 time=65.9 ms
4

Are you running Bind?

5

Hi @joseph

The Bind app is not installed.

I have a .local and **.fbx.one setup in Name Services.

Regards: peter

6

Is 10.64.XXX.YYY a shared connection internal interface or VPN?

If that’s shared then your setup may be very much like mine, except for the different resolve/not-resolve results we get. We can probably figure that out together.

7

Hi @joseph

There is not a shared interface. Below is a copy and paste for:

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 6c:4b:90:ee:9a:e9 brd ff:ff:ff:ff:ff:ff
    altname enx6c4b90ee9ae9
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 10:63:c8:e2:2f:c9 brd ff:ff:ff:ff:ff:ff
    altname wlx1063c8e22fc9
    inet 192.168.1.114/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 70514sec preferred_lft 70514sec
    inet6 fe80::46eb:492a:ddb0:556a/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
8

I’m not sure here, this sounds a little like network and a little like FreedomBox or application discriminating because of the request hostname (freedombox-home.local). The part where you can ping the freedombox-home.local sounds good for you from the network side.

Maybe hang on a bit and see if someone who’s better versed in the oidc authentication/authorization functionality chimes in. I don’t have much to offer about how that works.

9

Hi @joseph

Thanks for your help, like you said lets see if someone else can see what going wrong. Regards: peter

10

In the latest release we deployed OpenID Connect as the way to do single-sign-on. Very specific checks are made against the domain name before allowing single-sign-on in this way. The code here automatically allows all the domains listed in the in System → Name Services. Do you have freedombox-home set as your hostname? freedombox-home.local will show up in the list of configured domains there.

Also for debugging, please trying using another domain name or IP address to access your FreedomBox. The login might succeed this way.

11

Hi @Sunil

In the System > Name Service, section. The local hostname was: Freedombox-Home I changed this name to all lower case, freedombox-home and it as Solved the issue. I can now login to deluge with out a problem.

Regards: peter

2 Likes
12

Thank you for confirming. Casing of the hostname should not matter. We will fix this in the next release.