Jump to content

New QNAP Package for Testing


Recommended Posts

Posted

Hi, there is no more emby user or group.

 

What do you mean by tries to load https on the initial run?

Posted

Hi, there is no more emby user or group.

 

What do you mean by tries to load https on the initial run?

 

What I mean is when I install Emby and try to configure for the first time by clicking on the Emby Server icon, it tries to open Emby via https but it fails. I always configure my QNAP over https, maybe that has something to do with it.

Posted

Yea that's definitely not our doing. I wonder if it's related to something you configured in the community package.

Posted (edited)

What I mean is when I install Emby and try to configure for the first time by clicking on the Emby Server icon, it tries to open Emby via https but it fails. I always configure my QNAP over https, maybe that has something to do with it.

I already reported that a few posts ago but got no response. I still think its because the devs set an explicit https port for the emby package in QDK. In combination with the setting in qnap to always use https you cannot use the normal open function in qnap before having set up a ssl cert in emby.

 

Solution: Either remove the port in QDK configuration or provide a self signed cert automatically.

Edited by Fuechslein
Posted

@@Luke are you gonna answer my and others questions about the crash?

Im thinking to buy Emby Premiere, but if this error is popping up and the support is like this im not gonna buy it for sure.

Posted

I already reported that a few posts ago but got no response. I still think its because the devs set an explicit https port for the emby package in QDK. In combination with the setting in qnap to always use https you cannot use the normal open function in qnap before having set up a ssl cert in emby.

 

Solution: Either remove the port in QDK configuration or provide a self signed cert automatically.

I actually don't have my qnap set to always use https, but I was using https for my connection to the qnap. I'd prefer it if emby could use the https already configured on the qnap if possible.

Posted

@@Luke are you gonna answer my and others questions about the crash?

Im thinking to buy Emby Premiere, but if this error is popping up and the support is like this im not gonna buy it for sure.

 

Please try again and re-evaluate with the next update, thanks.

Posted

@@Luke thanks for the information.

I will wait for the update and let you know! :)

Posted

3.2.33.19 is up for testing:

  • Support volume selection
  • Fix dashboard opening up with ssl.

Thanks guys.

Posted

3.2.33.19 is up for testing:

  • Support volume selection
  • Fix dashboard opening up with ssl.
Thanks guys.

Hi Luke,

Ist it possible to update from the previous Version without rebuilding the entire media library?

It took quite a long time to get all the metadata after the last change.

Posted

From what previous version?

Posted

The one with the dedicated emby-user to the version 3.2.33.9.

Posted

The one with the dedicated emby-user to the version 3.2.33.9.

 

Ok, since that is a testing package, and things have changed since then, you'll have to just try it, sorry.

Posted

Ok, since that is a testing package, and things have changed since then, you'll have to just try it, sorry.

For sure. I will test it tomorrow (Timezone Germany) and give feedback.

Posted

Just upgrade from 33.9 to 33.19 without having to fetch all data again. All metadata have been kept.

 

However, I've  just realized that the "restart" function does not work anymore. Is there a known problem with one or the other plugin ?

 

Regards

Posted

I installed 3.2.33.19 without removing 3.2.33.9. It worked, all my previous settings and media lib remained as they were.

Posted

Just upgrade from 33.9 to 33.19 without having to fetch all data again. All metadata have been kept.

 

However, I've  just realized that the "restart" function does not work anymore. Is there a known problem with one or the other plugin ?

 

Regards

 

Can you describe what "doesn't work" means? thanks.

Posted

Clicking on Emby server icon still goes to HTTPS version and selects incorrect port.

For example: instead of going to https://mydomain.com:8921 , it goes to port 8920. Port 8921 is configured as HTTPS port. HTTPS is not required in the config settings either.

server-63644370995.txt

Posted

Clicking on Emby server icon still goes to HTTPS version and selects incorrect port.

For example: instead of going to https://mydomain.com:8921 , it goes to port 8920. Port 8921 is configured as HTTPS port. HTTPS is not required in the config settings either.

 

Does the community package do this?

Posted

Can you describe what "doesn't work" means? thanks.

I get the message that Emby Restart, but nothing happens. I need to go in the QNAP AppCenter and stop and restart the app to gain access again.

 

Regards,

Posted

I get the message that Emby Restart, but nothing happens. I need to go in the QNAP AppCenter and stop and restart the app to gain access again.

 

Regards,

 

What message exactly do you get? thanks.

Posted

Does the community package do this?

Community package goes to http version, even if https is checked off as required. However, it picks up the correct port for http -> port that is setup as http in config.

Posted (edited)

I saw the same restart problem on 3.2.33.9. Haven’t upgraded to newest yet. There was no warning or error messages it just sat there spinning.

Edited by syplex
Posted

I have upgraded to the new version, from 3.2.33.9 to.3.2.33.19. Stil after some minutes the server crashes.

 

What I have change in the settings:

 

- Https required on

- Selected my SSL pfx

- SSL password

 

The SSL seems to work but still I got servers crashes after some minutes.

 

Log file:

 

https://paste2.org/BgI5yz3P

 

What I am seeing is the same error as before with version 3.2.33.9

 

What to do next?

Posted

What message exactly do you get? thanks.

The pop up message from the emby server, stating it is restarting and that it can take 1 to 2 mins. However, I can wait forever and refresh the page, nothing comes back until I've restated the app in the AppCenter. The server is then accessible again within seeconds...

 

Regards,

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...