Abrasix 2 Posted November 25, 2023 Share Posted November 25, 2023 Hello world, Since I upgrade from FreeBSD 13.2 to FreeBSD 14.0, emby server can't be reach: ERR_CONNECTION_REFUSED It's the same from various web browser, or a smartTV apps... I check the FreeBSD connection, SSH is working, IP address is correct, but not the emby access. I've tried to reboot, or restart the service, and also to check the service status (it's running). Does someone is running emby on FreeBSD 14? Cheers, Abra 1 Link to comment Share on other sites More sharing options...
Luke 37068 Posted November 25, 2023 Share Posted November 25, 2023 Hi, is any emby server log file generated? Emby Server Data Folder Link to comment Share on other sites More sharing options...
Abrasix 2 Posted December 3, 2023 Author Share Posted December 3, 2023 Hi, Thank you for the tip, but there is no log in the log file: Quote # ls -l /var/db/emby-server/logs/ total 0 In addition, I can't simply stop the process: "service emby-server stop" never ends. I have to "kill -9" to get it terminated. I've tried to pkg remove && pkg install, but I face the same issues. Link to comment Share on other sites More sharing options...
Luke 37068 Posted December 5, 2023 Share Posted December 5, 2023 How did you install Emby Server? Link to comment Share on other sites More sharing options...
Abrasix 2 Posted December 5, 2023 Author Share Posted December 5, 2023 I have installed it with "pkg install emby-server" Here are my last checks: jellyfin is not working either, and there is no open socket: "sockstat -l" returns USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS alice sshd 77885 6 stream (not connected) root sshd 77879 6 stream (not connected) root sshd 1119 3 tcp6 *:22 *:* root sshd 1119 4 tcp4 *:22 *:* root syslogd 1032 6 udp6 *:514 *:* root syslogd 1032 7 udp4 *:514 *:* root syslogd 1032 8 dgram /var/run/log <- root syslogd 1032 9 dgram /var/run/logpriv root devd 828 4 stream /var/run/devd.pipe root devd 828 5 seqpac /var/run/devd.seqpacket.pipe Link to comment Share on other sites More sharing options...
Solution Duffyx 25 Posted December 6, 2023 Solution Share Posted December 6, 2023 Did you install openssl 1.1.1? Since the update to 3.X.X dotnet binaries are broken and fail to start any service. 3 Link to comment Share on other sites More sharing options...
Abrasix 2 Posted December 6, 2023 Author Share Posted December 6, 2023 Thank you Duffix and Luke for the help. "pkg install openssl" has solved the issue Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now