Page 1 of 1
Suddenly the console port seems unavailable
Posted:
Wed Feb 19, 2025 3:37 pmby n3mmr
I have my Serviio 2.3 running in a jail under TrueNAS Core 13.3.
The jail has the address <home-network>.199
IP scanners find the serviio jail and my media players can play stuff from the serviio dlna.
However, when I try to connect to "<home-network>.199:23523/console" with my browser, the connection times out. Same for the mediabrowser.
I need ideas on what might prevent reaching the console.
Re: Suddenly the console port seems unavailable
Posted:
Wed Feb 19, 2025 8:31 pmby atc98092
Just to confirm: this sandboxed place you run Serviio, the URL uses the .199, but not as a port? I could see your internal DNS have trouble resolving a URL that is using a number as the root of the network name. I don't know if that's something you've done intentionally, or if the system you're using did that by default. I could see the DLNA still functioning despite the naming, since it's using UDP and uPNP to discover the services. But I just have a hunch (with nothing to back it up) that your network name is the issue.
Re: Suddenly the console port seems unavailable
Posted:
Thu Feb 20, 2025 8:45 amby n3mmr
atc98092 wrote:Just to confirm: this sandboxed place you run Serviio, the URL uses the .199, but not as a port? I could see your internal DNS have trouble resolving a URL that is using a number as the root of the network name. I don't know if that's something you've done intentionally, or if the system you're using did that by default. I could see the DLNA still functioning despite the naming, since it's using UDP and uPNP to discover the services. But I just have a hunch (with nothing to back it up) that your network name is the issue.
using the DNS resolver to give the jail a name I tried
https://serviio2.rhg097:23523/console and got the same failure exactly.
I've had this serviio in that jail since 2.3 came out and the FreeBSD crowd hacked up a "port" that I found in freshports.org, which is the FreeBSD way to add non-BSD SW to the commonality.
The console has worked flawlessly in the manner described in my OP since I installed that jail, until a few days ago.
Re: Suddenly the console port seems unavailable
Posted:
Thu Feb 20, 2025 11:54 amby n3mmr
I got ssh running so I could run stuff in a better terminal window.
And I tried this inside the Serviio2 jail:
- Code:
[hans@Serviio2 ~]$ wget https://localhost:23523/console
--2025-02-20 12:51:34-- https://localhost:23523/console
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:23523... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:23523... failed: Connection refused.
So, nobody seems to be listening! Huh?????? What the f....!
Re: Suddenly the console port seems unavailable
Posted:
Thu Feb 20, 2025 1:17 pmby n3mmr
The port is 23423 for unsecure connection!
Gaah!
Re: Suddenly the console port seems unavailable
Posted:
Fri Feb 21, 2025 4:26 amby atc98092
Yes, 23423 is a standard port, while 23523 requires a security certificate of some sort installed on the machine with a FQDN that matches the machine. Beyond that, I'm outside my knowledge area with sandboxed or jailed apps. Hopefully someone else can step up here with some ideas.
Re: Suddenly the console port seems unavailable
Posted:
Mon Feb 24, 2025 3:11 pmby n3mmr
n3mmr wrote:The port is 23423 for unsecure connection!
Gaah!
And it now works.