Jump to content

Emby Server Port 80/443: Error in appHost.Init at Startup

dwalme

By dwalme
in Linux

 Share
Go to solution Solved by dwalme,

Recommended Posts

dwalme

dwalme 0

Posted
Posted

I have been trying to get my Emby Server to run on port 80 and 443 instead of the default ports of 8096 and 8920.   

Any time I change the server configuration for http to port 80 or the https port to 443 (with a valid certificate) Emby fails to start with the below error.

This has happened running Emby in docker on Debian 11, running native on Debian 11, and running native on Ubuntu 22.10.

Ports 80 and 443 or open on the host and this host that I have been testing with is dedicated to running Emby Server.

I have tried Emby Server v4.7.11.0 and beta v4.8.0.21.

What am I missing here? 

2023-01-10 17:13:14.229 Error Main: Error in appHost.Init
	*** Error Report ***
	Version: 4.7.11.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
	Operating system: Linux version 5.19.0-28-generic (buildd@lcy02-amd64-027) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-3ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.
	Framework: .NET 6.0.8
	OS/Process: x64/x64
	Runtime: opt/emby-server/system/System.Private.CoreLib.dll
	Processor count: 2
	Data path: /var/lib/emby
	Application path: /opt/emby-server/system
	System.Net.Sockets.SocketException: System.Net.Sockets.SocketException (13): Permission denied
	   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
	   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
	   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
	   at Emby.Server.Implementations.HttpServer.KestrelHost.KestrelListener.CreateBoundSocket(EndPoint endpoint)
	   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
	   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken)
	   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.TransportManager.BindAsync(EndPoint endPoint, ConnectionDelegate connectionDelegate, EndpointConfig endpointConfig, CancellationToken cancellationToken)
	   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.<>c__DisplayClass30_0`1.<<StartAsync>g__OnBind|0>d.MoveNext()
	--- End of stack trace from previous location ---
	   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context, CancellationToken cancellationToken)
	   at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
	   at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
	   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
	   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IEnumerable`1 listenOptions, AddressBindContext context, CancellationToken cancellationToken)
	   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.BindAsync(CancellationToken cancellationToken)
	   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken)
	   at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken)
	   at Microsoft.AspNetCore.Hosting.WebHost.Start()
	   at Emby.Server.Implementations.HttpServer.KestrelHost.KestrelListener.OnAddPrefixesComplete()
	   at Emby.Server.Implementations.ApplicationHost.Init()
	   at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken)
	Source: System.Net.Sockets
	TargetSite: Void UpdateStatusAfterSocketErrorAndThrowException(System.Net.Sockets.SocketError, System.String)

 

embyserver-63808967594.txt

Luke Emby Team

Luke 42077

Posted
Posted

Hi, this means the host system is denying the server permission to use that port (or something else is using it). As a test, you can try running the server elevated and that can help narrow down which of the two it is.

Happy2Play

Happy2Play 9780

Posted
Posted

Is something else on this system already using those ports?

dwalme

dwalme 0

Posted
  • Author
Posted (edited)
1 hour ago, Luke said:

Hi, this means the host system is denying the server permission to use that port (or something else is using it). As a test, you can try running the server elevated and that can help narrow down which of the two it is.

Ok so I ran /opt/emby-server/bin/emby-server as root and it started right up with port 80 and 443 defined.   Not sure why I did not think of that earlier.

Any idea what permissions need to be changed on Debian 11 or Ubuntu 22.10 in order to run the service as a regular user and have access to port 80 & 443?

 

 So it seems in Linux regular users are unable to bind to ports under 1024. Learn something new every day. 

Edited by dwalme
  • Solution
dwalme

dwalme 0

Posted
  • Author
  • Solution
Posted

Just to follow up here I found a couple workaround.

One option is to use authbind to allow binding to port 80/443.     That worked fine for running Emby Server natively on Linux.

 

The second option that worked for docker (and would work for running the server natively on Linux) is to change the unprivileged port from the default of 1024.

Add the following line to /etc/sysctl.conf: 

net.ipv4.ip_unprivileged_port_start=79

 

Both of these options reduce the security of the system so keep that in mind.

Q-Droid

Q-Droid 989

Posted
Posted

Yep. For the reasons you stated this is not the best approach and not needed for the vast majority of cases. For remote access a firewall/router can forward 80/443 to the Emby default ports 8096/8920. For both remote and local access a reverse proxy can do the same and be more secure than direct to Emby. 

dwalme

dwalme 0

Posted
  • Author
Posted

For external access I do use a reverse proxy. Adding another for internal use seems to add unnecessary complication and maintenance when a simple port change is all that is needed. 
 

I’ve been finding that the Emby clients are requiring me to manually type in my server address the first time in order to connect and having to append the port each time is a pain.

Perhaps there is another issue with the client autodiscovery but to me there’s no reason I cannot start with a single server name for all devices both internal and external.  Start simple and keep it simple.
https://emby1.domain.com works everywhere. 

Q-Droid

Q-Droid 989

Posted
Posted

A single reverse proxy can handle both external and internal connections. All I'm saying is that there are other ways that are not complicated and don't involve elevating privs or changing privileged port range. Not a big deal, it's your server after all and your choice. 

 

  • 2 years later...
camilia25

camilia25 0

Posted
Posted

The “Error in appHost.Init” on Emby Server using port 80/443 usually means those ports are already in use, often by another web service like Apache, Nginx, or system processes. To fix it, either change Emby to use a different port insystem.xml, or free up port 80/443 by stopping conflicting services. Reboot after changes to apply cleanly. I hope it helps!

  • 2 months later...
mx5gr

mx5gr 1

Posted
Posted

After updating from the 4.8 branch to the latest stable () on a Proxmox LXC, I got the following error when trying to launch under 443/SSL: 

2025-10-13T14:56:23.652522+03:00 emby emby-server[246]: Info App: Setting default culture to en-US
2025-10-13T14:56:23.657836+03:00 emby emby-server[246]: Info Main: Emby Server 4.9.1.80
2025-10-13T14:56:23.657997+03:00 emby emby-server[246]: #011Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
2025-10-13T14:56:23.658083+03:00 emby emby-server[246]: #011Operating system: Linux version 6.8.12-15-pve (build@proxmox) (gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX
2025-10-13T14:56:23.658174+03:00 emby emby-server[246]: #011OS/Process: x64/x64
2025-10-13T14:56:23.658201+03:00 emby emby-server[246]: #011Framework: .NET 8.0.11
2025-10-13T14:56:23.658230+03:00 emby emby-server[246]: #011Runtime: opt/emby-server/system/System.Private.CoreLib.dll
2025-10-13T14:56:23.658252+03:00 emby emby-server[246]: #011Processor count: 2
2025-10-13T14:56:23.658767+03:00 emby emby-server[246]: #011Data path: /var/lib/emby
2025-10-13T14:56:23.658804+03:00 emby emby-server[246]: #011Application path: /opt/emby-server/system
2025-10-13T14:56:23.658828+03:00 emby emby-server[246]: Info Main: Logs path: /var/lib/emby/logs
2025-10-13T14:56:23.658855+03:00 emby emby-server[246]: Info Main: Cache path: /var/lib/emby/cache
2025-10-13T14:56:23.658891+03:00 emby emby-server[246]: Info Main: Internal metadata path: /var/lib/emby/metadata
2025-10-13T14:56:23.658914+03:00 emby emby-server[246]: Info Main: DefaultThreadCurrentCulture: en-US
2025-10-13T14:56:23.658941+03:00 emby emby-server[246]: Info Main: DefaultThreadCurrentUICulture: en-US
2025-10-13T14:56:23.658963+03:00 emby emby-server[246]: Info Main: DefaultThreadCurrentUICulture: en-US
2025-10-13T14:56:23.661669+03:00 emby emby-server[246]: Info Main: Server Friendly Name: ‌emby‌
2025-10-13T14:56:23.662333+03:00 emby emby-server[246]: Info Main: Local time: 10/13/2025 14:56:23 +03:00
2025-10-13T14:56:23.669282+03:00 emby emby-server[246]: Info App: Emby Server Version: 4.9.1.80
2025-10-13T14:56:23.670565+03:00 emby emby-server[246]: Info App: Loading assemblies
.
.
.
2025-10-13T14:56:24.147890+03:00 emby emby-server[246]: Info NetworkManager: Detecting local network addresses
2025-10-13T14:56:24.148557+03:00 emby emby-server[246]: Info NetworkManager: networkInterface: Ethernet eth0, Speed: 10000000000, Description: eth0
2025-10-13T14:56:24.151326+03:00 emby emby-server[246]: Info NetworkManager: GatewayAddresses: 192.168.100.1
2025-10-13T14:56:24.158207+03:00 emby emby-server[246]: Info NetworkManager: UnicastAddresses: 192.168.100.25,fe80::be24:11ff:f128:39fe%2
2025-10-13T14:56:24.158435+03:00 emby emby-server[246]: Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo
2025-10-13T14:56:24.158506+03:00 emby emby-server[246]: Info NetworkManager: GatewayAddresses:
2025-10-13T14:56:24.158531+03:00 emby emby-server[246]: Info NetworkManager: UnicastAddresses: 127.0.0.1,::1
2025-10-13T14:56:24.189048+03:00 emby emby-server[246]: Info NetworkManager: Detected local ip addresses: [{"IPAddress":"192.168.100.25","HasGateWayAddress":true,"PrefixLength":24,"IPv4Mask":"255.255.255.0"},{"IPAddress":"fe80::be24:11ff:f128:39fe%2","HasGateWayAddress":true,"PrefixLength":64},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"},{"IPAddress":"::1","HasGateWayAddress":false,"PrefixLength":128}]
2025-10-13T14:56:24.196072+03:00 emby emby-server[246]: Info App: Adding HttpListener prefix http://+:8096/
2025-10-13T14:56:24.196172+03:00 emby emby-server[246]: Info App: Adding HttpListener prefix https://+:443/
2025-10-13T14:56:24.200513+03:00 emby systemd-networkd[113]: eth0: Gained IPv6LL
2025-10-13T14:56:24.421631+03:00 emby emby-server[246]: Error Main: Error in appHost.Init
2025-10-13T14:56:24.421713+03:00 emby emby-server[246]: #011*** Error Report ***
2025-10-13T14:56:24.421737+03:00 emby emby-server[246]: #011Version: 4.9.1.80
2025-10-13T14:56:24.421760+03:00 emby emby-server[246]: #011Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
2025-10-13T14:56:24.421783+03:00 emby emby-server[246]: #011Operating system: Linux version 6.8.12-15-pve (build@proxmox) (gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX
2025-10-13T14:56:24.421805+03:00 emby emby-server[246]: #011OS/Process: x64/x64
2025-10-13T14:56:24.421826+03:00 emby emby-server[246]: #011Framework: .NET 8.0.11
2025-10-13T14:56:24.421847+03:00 emby emby-server[246]: #011Runtime: opt/emby-server/system/System.Private.CoreLib.dll
2025-10-13T14:56:24.421868+03:00 emby emby-server[246]: #011Processor count: 2
2025-10-13T14:56:24.421890+03:00 emby emby-server[246]: #011Data path: /var/lib/emby
2025-10-13T14:56:24.421911+03:00 emby emby-server[246]: #011Application path: /opt/emby-server/system
2025-10-13T14:56:24.421932+03:00 emby emby-server[246]: #011System.Net.Sockets.SocketException: System.Net.Sockets.SocketException (13): Permission denied
2025-10-13T14:56:24.421959+03:00 emby emby-server[246]: #011   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
2025-10-13T14:56:24.421987+03:00 emby emby-server[246]: #011   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
2025-10-13T14:56:24.422008+03:00 emby emby-server[246]: #011   at Emby.Server.Implementations.HttpServer.KestrelHost.KestrelListener.CreateBoundSocket(EndPoint endpoint)
2025-10-13T14:56:24.422030+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
2025-10-13T14:56:24.422051+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken)
2025-10-13T14:56:24.422082+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.TransportManager.BindAsync(EndPoint endPoint, ConnectionDelegate connectionDelegate, EndpointConfig endpointConfig, CancellationToken cancellationToken)
2025-10-13T14:56:24.422138+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.<>c__DisplayClass28_0`1.<<StartAsync>g__OnBind|0>d.MoveNext()
2025-10-13T14:56:24.422178+03:00 emby emby-server[246]: #011--- End of stack trace from previous location ---
2025-10-13T14:56:24.422200+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context, CancellationToken cancellationToken)
2025-10-13T14:56:24.422222+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
2025-10-13T14:56:24.422262+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
2025-10-13T14:56:24.422289+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
2025-10-13T14:56:24.422312+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(ListenOptions[] listenOptions, AddressBindContext context, Func`2 useHttps, CancellationToken cancellationToken)
2025-10-13T14:56:24.422339+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.BindAsync(CancellationToken cancellationToken)
2025-10-13T14:56:24.422361+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken)
2025-10-13T14:56:24.422382+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken)
2025-10-13T14:56:24.422404+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Hosting.WebHost.Start()
2025-10-13T14:56:24.422426+03:00 emby emby-server[246]: #011   at Emby.Server.Implementations.HttpServer.KestrelHost.KestrelListener.OnAddPrefixesComplete()
2025-10-13T14:56:24.422452+03:00 emby emby-server[246]: #011   at Emby.Server.Implementations.HttpServer.HttpListenerHost.OnAddPrefixesComplete()
2025-10-13T14:56:24.422474+03:00 emby emby-server[246]: #011   at Emby.Server.Implementations.ApplicationHost.StartServer()
2025-10-13T14:56:24.422495+03:00 emby emby-server[246]: #011   at Emby.Server.Implementations.ApplicationHost.Init()
2025-10-13T14:56:24.422516+03:00 emby emby-server[246]: #011   at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken)
2025-10-13T14:56:24.422547+03:00 emby emby-server[246]: #011Source: System.Net.Sockets
2025-10-13T14:56:24.422572+03:00 emby emby-server[246]: #011TargetSite: Void DoBind(System.Net.EndPoint, System.Net.SocketAddress)
2025-10-13T14:56:24.422597+03:00 emby emby-server[246]: #011
2025-10-13T14:56:24.423287+03:00 emby emby-server[246]: Info Main: Shutdown complete
2025-10-13T14:56:24.423543+03:00 emby emby-server[246]: Info LogManager: Disposing Logger
2025-10-13T14:56:24.436488+03:00 emby systemd[1]: emby-server.service: Deactivated successfully.
2025-10-13T14:56:24.436592+03:00 emby systemd[1]: emby-server.service: Consumed 1.006s CPU time, 136.6M memory peak.

I tried to add the solution above to /etc/sysctl.conf, to no avail.. the error persists.

It is clearly an elevated rights issue, as launching the Emby server under the root user works perfectly.

Any ideas?

Luke Emby Team

Luke 42077

Posted
Posted
1 hour ago, mx5gr said:

After updating from the 4.8 branch to the latest stable () on a Proxmox LXC, I got the following error when trying to launch under 443/SSL: 

2025-10-13T14:56:23.652522+03:00 emby emby-server[246]: Info App: Setting default culture to en-US
2025-10-13T14:56:23.657836+03:00 emby emby-server[246]: Info Main: Emby Server 4.9.1.80
2025-10-13T14:56:23.657997+03:00 emby emby-server[246]: #011Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
2025-10-13T14:56:23.658083+03:00 emby emby-server[246]: #011Operating system: Linux version 6.8.12-15-pve (build@proxmox) (gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX
2025-10-13T14:56:23.658174+03:00 emby emby-server[246]: #011OS/Process: x64/x64
2025-10-13T14:56:23.658201+03:00 emby emby-server[246]: #011Framework: .NET 8.0.11
2025-10-13T14:56:23.658230+03:00 emby emby-server[246]: #011Runtime: opt/emby-server/system/System.Private.CoreLib.dll
2025-10-13T14:56:23.658252+03:00 emby emby-server[246]: #011Processor count: 2
2025-10-13T14:56:23.658767+03:00 emby emby-server[246]: #011Data path: /var/lib/emby
2025-10-13T14:56:23.658804+03:00 emby emby-server[246]: #011Application path: /opt/emby-server/system
2025-10-13T14:56:23.658828+03:00 emby emby-server[246]: Info Main: Logs path: /var/lib/emby/logs
2025-10-13T14:56:23.658855+03:00 emby emby-server[246]: Info Main: Cache path: /var/lib/emby/cache
2025-10-13T14:56:23.658891+03:00 emby emby-server[246]: Info Main: Internal metadata path: /var/lib/emby/metadata
2025-10-13T14:56:23.658914+03:00 emby emby-server[246]: Info Main: DefaultThreadCurrentCulture: en-US
2025-10-13T14:56:23.658941+03:00 emby emby-server[246]: Info Main: DefaultThreadCurrentUICulture: en-US
2025-10-13T14:56:23.658963+03:00 emby emby-server[246]: Info Main: DefaultThreadCurrentUICulture: en-US
2025-10-13T14:56:23.661669+03:00 emby emby-server[246]: Info Main: Server Friendly Name: ‌emby‌
2025-10-13T14:56:23.662333+03:00 emby emby-server[246]: Info Main: Local time: 10/13/2025 14:56:23 +03:00
2025-10-13T14:56:23.669282+03:00 emby emby-server[246]: Info App: Emby Server Version: 4.9.1.80
2025-10-13T14:56:23.670565+03:00 emby emby-server[246]: Info App: Loading assemblies
.
.
.
2025-10-13T14:56:24.147890+03:00 emby emby-server[246]: Info NetworkManager: Detecting local network addresses
2025-10-13T14:56:24.148557+03:00 emby emby-server[246]: Info NetworkManager: networkInterface: Ethernet eth0, Speed: 10000000000, Description: eth0
2025-10-13T14:56:24.151326+03:00 emby emby-server[246]: Info NetworkManager: GatewayAddresses: 192.168.100.1
2025-10-13T14:56:24.158207+03:00 emby emby-server[246]: Info NetworkManager: UnicastAddresses: 192.168.100.25,fe80::be24:11ff:f128:39fe%2
2025-10-13T14:56:24.158435+03:00 emby emby-server[246]: Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo
2025-10-13T14:56:24.158506+03:00 emby emby-server[246]: Info NetworkManager: GatewayAddresses:
2025-10-13T14:56:24.158531+03:00 emby emby-server[246]: Info NetworkManager: UnicastAddresses: 127.0.0.1,::1
2025-10-13T14:56:24.189048+03:00 emby emby-server[246]: Info NetworkManager: Detected local ip addresses: [{"IPAddress":"192.168.100.25","HasGateWayAddress":true,"PrefixLength":24,"IPv4Mask":"255.255.255.0"},{"IPAddress":"fe80::be24:11ff:f128:39fe%2","HasGateWayAddress":true,"PrefixLength":64},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"},{"IPAddress":"::1","HasGateWayAddress":false,"PrefixLength":128}]
2025-10-13T14:56:24.196072+03:00 emby emby-server[246]: Info App: Adding HttpListener prefix http://+:8096/
2025-10-13T14:56:24.196172+03:00 emby emby-server[246]: Info App: Adding HttpListener prefix https://+:443/
2025-10-13T14:56:24.200513+03:00 emby systemd-networkd[113]: eth0: Gained IPv6LL
2025-10-13T14:56:24.421631+03:00 emby emby-server[246]: Error Main: Error in appHost.Init
2025-10-13T14:56:24.421713+03:00 emby emby-server[246]: #011*** Error Report ***
2025-10-13T14:56:24.421737+03:00 emby emby-server[246]: #011Version: 4.9.1.80
2025-10-13T14:56:24.421760+03:00 emby emby-server[246]: #011Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
2025-10-13T14:56:24.421783+03:00 emby emby-server[246]: #011Operating system: Linux version 6.8.12-15-pve (build@proxmox) (gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX
2025-10-13T14:56:24.421805+03:00 emby emby-server[246]: #011OS/Process: x64/x64
2025-10-13T14:56:24.421826+03:00 emby emby-server[246]: #011Framework: .NET 8.0.11
2025-10-13T14:56:24.421847+03:00 emby emby-server[246]: #011Runtime: opt/emby-server/system/System.Private.CoreLib.dll
2025-10-13T14:56:24.421868+03:00 emby emby-server[246]: #011Processor count: 2
2025-10-13T14:56:24.421890+03:00 emby emby-server[246]: #011Data path: /var/lib/emby
2025-10-13T14:56:24.421911+03:00 emby emby-server[246]: #011Application path: /opt/emby-server/system
2025-10-13T14:56:24.421932+03:00 emby emby-server[246]: #011System.Net.Sockets.SocketException: System.Net.Sockets.SocketException (13): Permission denied
2025-10-13T14:56:24.421959+03:00 emby emby-server[246]: #011   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
2025-10-13T14:56:24.421987+03:00 emby emby-server[246]: #011   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
2025-10-13T14:56:24.422008+03:00 emby emby-server[246]: #011   at Emby.Server.Implementations.HttpServer.KestrelHost.KestrelListener.CreateBoundSocket(EndPoint endpoint)
2025-10-13T14:56:24.422030+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
2025-10-13T14:56:24.422051+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken)
2025-10-13T14:56:24.422082+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.TransportManager.BindAsync(EndPoint endPoint, ConnectionDelegate connectionDelegate, EndpointConfig endpointConfig, CancellationToken cancellationToken)
2025-10-13T14:56:24.422138+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.<>c__DisplayClass28_0`1.<<StartAsync>g__OnBind|0>d.MoveNext()
2025-10-13T14:56:24.422178+03:00 emby emby-server[246]: #011--- End of stack trace from previous location ---
2025-10-13T14:56:24.422200+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context, CancellationToken cancellationToken)
2025-10-13T14:56:24.422222+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
2025-10-13T14:56:24.422262+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
2025-10-13T14:56:24.422289+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
2025-10-13T14:56:24.422312+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(ListenOptions[] listenOptions, AddressBindContext context, Func`2 useHttps, CancellationToken cancellationToken)
2025-10-13T14:56:24.422339+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.BindAsync(CancellationToken cancellationToken)
2025-10-13T14:56:24.422361+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken)
2025-10-13T14:56:24.422382+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken)
2025-10-13T14:56:24.422404+03:00 emby emby-server[246]: #011   at Microsoft.AspNetCore.Hosting.WebHost.Start()
2025-10-13T14:56:24.422426+03:00 emby emby-server[246]: #011   at Emby.Server.Implementations.HttpServer.KestrelHost.KestrelListener.OnAddPrefixesComplete()
2025-10-13T14:56:24.422452+03:00 emby emby-server[246]: #011   at Emby.Server.Implementations.HttpServer.HttpListenerHost.OnAddPrefixesComplete()
2025-10-13T14:56:24.422474+03:00 emby emby-server[246]: #011   at Emby.Server.Implementations.ApplicationHost.StartServer()
2025-10-13T14:56:24.422495+03:00 emby emby-server[246]: #011   at Emby.Server.Implementations.ApplicationHost.Init()
2025-10-13T14:56:24.422516+03:00 emby emby-server[246]: #011   at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken)
2025-10-13T14:56:24.422547+03:00 emby emby-server[246]: #011Source: System.Net.Sockets
2025-10-13T14:56:24.422572+03:00 emby emby-server[246]: #011TargetSite: Void DoBind(System.Net.EndPoint, System.Net.SocketAddress)
2025-10-13T14:56:24.422597+03:00 emby emby-server[246]: #011
2025-10-13T14:56:24.423287+03:00 emby emby-server[246]: Info Main: Shutdown complete
2025-10-13T14:56:24.423543+03:00 emby emby-server[246]: Info LogManager: Disposing Logger
2025-10-13T14:56:24.436488+03:00 emby systemd[1]: emby-server.service: Deactivated successfully.
2025-10-13T14:56:24.436592+03:00 emby systemd[1]: emby-server.service: Consumed 1.006s CPU time, 136.6M memory peak.

I tried to add the solution above to /etc/sysctl.conf, to no avail.. the error persists.

It is clearly an elevated rights issue, as launching the Emby server under the root user works perfectly.

Any ideas?

HI @mx5gris there something special you need to do to grant the server access to use port 443?

mx5gr

mx5gr 1

Posted
Posted

The issue occurred with the .NET 8 adoption. Up to now, the 4.8.x branch, everything was working flawlessly.

I changed the systemd service user from "emby" to "root" as an interim solution and the service launches fine using SSL port 443 instead of 8920 (similarly to when executing the binary from the command prompt, under elevated rights).

I installed the emby Proxmox LXC emby via an installation script (https://community-scripts.github.io/ProxmoxVE/scripts?id=emby) and updated to the latest release through the "update" command, as suggested.

It is surely a rights issue of the user that launches the service (emby) which appeared under .NET 8. As stated previously, the  

net.ipv4.ip_unprivileged_port_start=79

workaround did not work.

I am not sure what you mean with "something special".

Luke Emby Team

Luke 42077

Posted
Posted
Quote

I am not sure what you mean with "something special".

I just meant anything that might of interest in terms of helping to get to the bottom of this.

Did you figure anything out?

mx5gr

mx5gr 1

Posted
Posted

Unfortunately not... but Ι'm open to suggestions on where to look!

Luke Emby Team

Luke 42077

Posted
Posted

Have you tried running as sudo as a test?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...