Jump to content

Some issues with FreeBSD Plugin on FreeNAS


Recommended Posts

Bolo Popo
Posted

Hello,

 

I'm running the emby plugin (4.6.4.0) via an 'vanilla' install on FreeNAS-11.3-U5.

I say vanilla because I didn't change anything at install time except to mount a volume for my media...

(Actually I think I clicked for DHCP instead of NAT, and clicked 'Autoconfigure IPv6', but other than that...)

For some reason the server isn't listening on the https port. From another jail on the same FreeNAS box I can only see port 8096 open and not 8920.

I went to the trouble of getting a cert for my ddns domain name to get https over remote connections without errors, but without port 8920 open it obviously doesn't work...

 

Not sure what I'm doing wrong! I'm set to just re-install the plugin and try again?

Should I try installing via 'pkg'?

 

 

Many thanks,
Dan.

 

 

Bolo Popo
Posted

Just tried installing via pkg on a 'fresh' jail running 11.4-RELEASE-p6 and I get the same issue.

I'm tempted to think that there is simply a missing ssl or tls library needed?

 

Many thanks,
Dan.

Bolo Popo
Posted (edited)

I think the lack of https is stopping my Roku device from being able to connect... Not 100% sure, but it fails to see the server (using the http port obvs.)

EDIT: The Roku connection issue had nothing to do with http vs. https, I was using the wrong port number to connect because I forwarded the standard Emby http port to a random port number on the WAN side of my router.

Edited by Bolo Popo
Clarifying an unrelated side issue.
Bolo Popo
Posted

This is really frustrating. How come the server isn't listening on HTTPS?

Posted

Hi @Bolo Popo did you configure the certificate in Emby Server network settings?

Bolo Popo
Posted

Yes I did, but it should be listening on https on the LAN even without this.

I used certbot to generate a certificate for my ddns domain name and I put it into the appropriate box in the network config.

  • 2 weeks later...
Posted
On 8/8/2021 at 5:35 AM, Bolo Popo said:

Yes I did, but it should be listening on https on the LAN even without this.

I used certbot to generate a certificate for my ddns domain name and I put it into the appropriate box in the network config.

Hi, it is listening, but it only shows https on the server dashboard if the certificate has loaded successfully, so I'm guessing that didn't happen.

Please attach the emby server log and I'm guessing it will show an error related to your certificate.

Posted

netstat on the emby jail says differently, but I'll paste the log...

Before I do that, is there anything sensitive I should expunge from the log? Will grepping the log for 'error' be enough?

 

Many thanks for help,

 

Posted

I am seeing several errors like this, not sure if they are transient or related:

2021-08-16 16:19:02.822 Info HttpClient: HttpClientManager GET: https://www.mb3admin.com/admin/service/EmbyPackages.json
2021-08-16 16:19:15.941 Error HttpClient: Error NameResolutionFailure getting response from 
	*** Error Report ***
	Version: 4.6.4.0
	Command line: /usr/local/lib/emby-server/system/EmbyServer.exe -os freebsd -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server -updatepackage emby-server-freebsd_{version}_amd64.txz -noautorunwebapp
	Operating system: Unix 11.3.14.0 
	Framework: Mono: 5.10.1.57 (5.10.1.57 Sat Jul 10 02:33:45 UTC 2021)
	OS/Process: X64/X64
	Runtime: usr/local/lib/mono/4.5/mscorlib.dll
	Processor count: 4
	Data path: /var/db/emby-server
	Application path: /usr/local/lib/emby-server/system
	System.Net.WebException: System.Net.WebException: Error: NameResolutionFailure
	  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00058] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 
	  at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <0e06830de9a44394a7e366951eabca52>:0 
	Source: System
	TargetSite: System.Net.WebResponse EndGetResponse(System.IAsyncResult)
	
2021-08-16 16:19:15.942 Info App: Timed out checking for application updates. Will try again later
2021-08-16 16:19:15.942 Debug TaskManager: Check for application updates Completed after 0 minute(s) and 15 seconds

 

Posted

Also:

[root@emby-pkg /]# nmap localhost -p 0-65535
Starting Nmap 7.91 ( https://nmap.org ) at 2021-08-18 10:17 BST
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000067s latency).
Other addresses for localhost (not scanned): ::1
Not shown: 65535 closed ports
PORT     STATE SERVICE
8096/tcp open  unknown

Nmap done: 1 IP address (1 host up) scanned in 352.82 seconds

 

Posted
On 8/18/2021 at 5:12 AM, Bolo Popo said:

I am seeing several errors like this, not sure if they are transient or related:


2021-08-16 16:19:02.822 Info HttpClient: HttpClientManager GET: https://www.mb3admin.com/admin/service/EmbyPackages.json
2021-08-16 16:19:15.941 Error HttpClient: Error NameResolutionFailure getting response from 
	*** Error Report ***
	Version: 4.6.4.0
	Command line: /usr/local/lib/emby-server/system/EmbyServer.exe -os freebsd -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server -updatepackage emby-server-freebsd_{version}_amd64.txz -noautorunwebapp
	Operating system: Unix 11.3.14.0 
	Framework: Mono: 5.10.1.57 (5.10.1.57 Sat Jul 10 02:33:45 UTC 2021)
	OS/Process: X64/X64
	Runtime: usr/local/lib/mono/4.5/mscorlib.dll
	Processor count: 4
	Data path: /var/db/emby-server
	Application path: /usr/local/lib/emby-server/system
	System.Net.WebException: System.Net.WebException: Error: NameResolutionFailure
	  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00058] in <b3922b7d60404fa9ae645f1fb97f5b6b>:0 
	  at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <0e06830de9a44394a7e366951eabca52>:0 
	Source: System
	TargetSite: System.Net.WebResponse EndGetResponse(System.IAsyncResult)
	
2021-08-16 16:19:15.942 Info App: Timed out checking for application updates. Will try again later
2021-08-16 16:19:15.942 Debug TaskManager: Check for application updates Completed after 0 minute(s) and 15 seconds

 

That's not related to this.

Posted
On 8/18/2021 at 4:56 AM, Bolo Popo said:

netstat on the emby jail says differently, but I'll paste the log...

Before I do that, is there anything sensitive I should expunge from the log? Will grepping the log for 'error' be enough?

 

Many thanks for help,

 

Please attach the complete emby server log, or send to me via PM. Thanks.

  • 4 weeks later...
Posted (edited)

Sorry it's taken so long to get back to you on this, I'll PM you the log...

Done

Edited by Bolo Popo
Done
Posted

Hi, please take a look at the advice in this topic and see if it helps:

Thanks.

Posted (edited)

Thanks @Luke, Please note that this is an issue with the plugin, not the package, and I've tried re-installing both flavours (twice) in new jails and I still see the issue... not sure if I'm doing something wrong :(

I can pick the version of freenas that the jail uses if you think that will help?

Edited by Bolo Popo
Confused the word 'package' for 'jail'
Posted

Do I just need to run cert-sync?

 

Posted
1 hour ago, Bolo Popo said:

Do I just need to run cert-sync?

 

It's worth trying, yes.

  • 2 weeks later...
Posted

Didn't seem to do anything.

 

Posted

I can reproduce this on re-install.

  • 1 month later...
Posted

By getting and then converting a LetsEncrypt cert and then uploading to Emby, I can fix the issue. Would be nice if the install created a new cert.

Posted

Not sure why all the tutorials I read seem to imply that https will 'just work' without getting (and potentially converting) and uploading the cert... would be nice to have a tutorial on that.

Posted
2 hours ago, Bolo Popo said:

By getting and then converting a LetsEncrypt cert and then uploading to Emby, I can fix the issue. Would be nice if the install created a new cert.

Thanks for the feedback.

Posted
2 hours ago, Bolo Popo said:

Not sure why all the tutorials I read seem to imply that https will 'just work' without getting (and potentially converting) and uploading the cert... would be nice to have a tutorial on that.

There are actually a number of them, albeit spread throughout the community.

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
×
×
  • Create New...