server running only on HTTP, has no HTTPS access..

[Dariusz 25]

i'm pretty sure this isn't a certificate issue as I am able to use the domain to enter the server under HTTP, and it worked fine when i ran it on my old server under a different platform.. however when i switched to TrueNAS CORE, i am unable to access the server using SSL..

if i recall, emby server would normally say it was running on HTTP and HTTPS ports.. but mine says it's just running under HTTP port, no mention of HTTPS.. am i missing something here? Something i might need to enable?

I am forwarding both ports (for now until i get HTTPS to work).. i think all emby settings are correct from what I could locate based on other peoples posts and my previous server settings.. but emby always shows my Remote (WAN) as HTTP only..

 

 

embyserver (2).txt

[Luke 42077]

HI, smb paths are currently not supported for the certificate. You'll have to give it a natively supported path, e.g. /file/xyz.pfx. So usually that means being a file on the server machine.

[Dariusz 25]

2 hours ago, Luke said:

HI, smb paths are currently not supported for the certificate. You'll have to give it a natively supported path, e.g. /file/xyz.pfx. So usually that means being a file on the server machine.

Amazing! This fixed my issue.. and i was going crazy over what i might of have missed lol.. I really appreciate the quick reply on this.. 

On a side note, your advice also fixed a second issue i was battling with, backing up EMBY server kept on failing for me.. as soon as i moved the backup to a native path, it worked.. 

[Luke 42077]

Right smb protocol support is not native to the platform but rather it's something that is built into Emby Server. But there are a few outstanding cases here and there that haven't added support for it yet. Thanks.