You need to proxy pass to https://(your documentserver url)

hi all

 

is it normal that docker h265 eat all my cpu power.

 

I got an i7 7700 and if i start the docker it eat up the cpu.

 

Everything is in fastest mode

hi all
 
is it normal that docker h265 eat all my cpu power.
 
I got an i7 7700 and if i start the docker it eat up the cpu.
 
Everything is in fastest mode

Yes, this is normal, it will use all the CPU for encoding, I suggest you pin the CPU core to restrict it's usage

Sent from my Pixel 3 using Tapatalk

4 minutes ago, Siwat2545 said:

Yes, this is normal, it will use all the CPU for encoding, I suggest you pin the CPU core to restrict it's usage

Sent from my Pixel 3 using Tapatalk
 

Good idea thx

 

On 12/27/2018 at 3:01 AM, Siwat2545 said:

You need to proxy pass to https://(your documentserver url)

Hmm, I still get a 502 bad gateway using https:

 

# only office doc server

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name docs.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_docs onlyofficedocumentserver;
        proxy_pass https://$upstream_docs;
    }
}

I'm trying to use the same format as the rest of the proxy confs in the LetsEncrypt folder, but I'm not sure if there's something going wrong there or a better way to do this.  If I remove all the "resolver" and set $upstream stuff in favor of a straight proxy_pass https://unraidIP:4432, the LetsEncrypt docker throws a ton of variable errors and fails to start.  Do you happen to have this running behind the LetsEncrypt container?

 

Edit: Got it figured out.  From a tip in another thread, you have to actually change the name of the Docker container to all lowercase, then the 502 will go away.  I then used this config:

 

server {
    listen 443 ssl;

    server_name docs.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;


    location / {
				include /config/nginx/proxy.conf;
				resolver 127.0.0.11 valid=30s;
                set $upstream_docs onlyofficedocumentserver;
				proxy_pass https://$upstream_docs:443;
                proxy_redirect off;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Host $server_name;
                proxy_set_header X-Forwarded-Proto $scheme;
        }
}

 

After this, I just went back into the OnlyOffice plugin settings, then entered the https address into the settings and voila!  I can open docs in NextCloud now!

Edited January 4, 20197 yr by Coolsaber57

On 1/4/2019 at 3:38 AM, Coolsaber57 said:

Hmm, I still get a 502 bad gateway using https:

 

# only office doc server

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name docs.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_docs onlyofficedocumentserver;
        proxy_pass https://$upstream_docs;
    }
}

I'm trying to use the same format as the rest of the proxy confs in the LetsEncrypt folder, but I'm not sure if there's something going wrong there or a better way to do this.  If I remove all the "resolver" and set $upstream stuff in favor of a straight proxy_pass https://unraidIP:4432, the LetsEncrypt docker throws a ton of variable errors and fails to start.  Do you happen to have this running behind the LetsEncrypt container?

 

Edit: Got it figured out.  From a tip in another thread, you have to actually change the name of the Docker container to all lowercase, then the 502 will go away.  I then used this config:

 

server {
    listen 443 ssl;

    server_name docs.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;


    location / {
				include /config/nginx/proxy.conf;
				resolver 127.0.0.11 valid=30s;
                set $upstream_docs onlyofficedocumentserver;
				proxy_pass https://$upstream_docs:443;
                proxy_redirect off;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Host $server_name;
                proxy_set_header X-Forwarded-Proto $scheme;
        }
}

 

After this, I just went back into the OnlyOffice plugin settings, then entered the https address into the settings and voila!  I can open docs in NextCloud now!

Glad to hear that it worked! I might add this to the FAQ soon.

Hi please add to you container package iputils-ping as some plugins for home bridge required ping package like homebridge-samsung-tizen

 

Thanks

On 1/16/2019 at 1:29 AM, piotrasd said:

Hi please add to you container package iputils-ping as some plugins for home bridge required ping package like homebridge-samsung-tizen

 

Thanks

You need to use the packages and apt-packages variable

Can someone help me with the Facebox docker at all? Starting to lose my mind...

No mater what I do, when i start it, the logs always say "[ERROR] MB_KEY: Invalid MB_KEY"

 

S: any ideas would be appreciated.

2 minutes ago, ampm-it said:

Can someone help me with the Facebox docker at all? Starting to lose my mind...

No mater what I do, when i start it, the logs always say "[ERROR] MB_KEY: Invalid MB_KEY"

 

S: any ideas would be appreciated.

Maybe obvious, but since you don't say so, did you enter a key?

6 hours ago, trurl said:

Maybe obvious, but since you don't say so, did you enter a key?

Opps.

Yes entered the api key provided by Machine Box.

In the "API_KEY" Setting I have tried the following

Key: MB_KEY=

Value: api key

 

Key: MB_KEY=api key

Value: api key

 

Key: MB_KEY=api key

Value: MB_KEY=api key

 

Unless its an issue with nthe api key needing the " before and after it, But the moment I put that in unraid removes the entire key...

 

Thanks for the Phlex container Siwat2545!

 

Has anyone managed to reverse proxy it through nginx? Tried a few different configs but couldn't get it to work. Seems like it might need a baseurl set in the app?

 

Tempted to change to use phlex.domain.com instead of domain.com/phlex and see if that works.

Thanks for the Phlex container Siwat2545!
 
Has anyone managed to reverse proxy it through nginx? Tried a few different configs but couldn't get it to work. Seems like it might need a baseurl set in the app?
 
Tempted to change to use phlex.domain.com instead of domain.com/phlex and see if that works.

You need to use phlex.domain.com, also you need to set base url in setting of phlex

Sent from my Pixel 3 using Tapatalk

Opps.
Yes entered the api key provided by Machine Box.
In the "API_KEY" Setting I have tried the following
Key: MB_KEY=
Value: api key
 
Key: MB_KEY=api key
Value: api key
 
Key: MB_KEY=api key
Value: MB_KEY=api key
 
Unless its an issue with nthe api key needing the " before and after it, But the moment I put that in unraid removes the entire key...
 

Key: MB_KEY
Value: [Your API Key]

Sent from my Pixel 3 using Tapatalk

22 hours ago, Siwat2545 said:

You need to use phlex.domain.com, also you need to set base url in setting of phlex

Sent from my Pixel 3 using Tapatalk
 

Thanks, thought so. Do you have it working with the subdomain? If so are you able to share the config you are using?

Thanks, thought so. Do you have it working with the subdomain? If so are you able to share the config you are using?

I have it working with subdomain, in the config of phlex, enter https://[yoursubdomain]:443
Note that the url is https as Google and Alexa won't accept http unencrypted

Sent from my Pixel 3 using Tapatalk

I have it working with subdomain, in the config of phlex, enter https://[yoursubdomain]:443
Note that the url is https as Google and Alexa won't accept http unencrypted

Sent from my Pixel 3 using Tapatalk

Here's my config

Sent from my Pixel 3 using Tapatalk

5 hours ago, Siwat2545 said:

Here's my config

Sent from my Pixel 3 using Tapatalk
 

Apologies, I meant the nginx config (if you are using nginx)

4 hours ago, itsdandandan said:

Apologies, I meant the nginx config (if you are using nginx)

I'm actually using HAProxy, sorry

Heya guys,

 

the homebridge-hue plugin is too new for the current homebridge-with-gui docker.

I get this error:

Error: Plugin /usr/local/lib/node_modules/homebridge-hue requires a HomeBridge version of ^0.4.46 which does not satisfy the current HomeBridge version of 0.4.45. You may need to upgrade your installation of HomeBridge.

Any docker update soon? :)

 

Thanks and keep up the good work!

Tschuki

Heya guys,
 
the homebridge-hue plugin is too new for the current homebridge-with-gui docker.
I get this error:

Error: Plugin /usr/local/lib/node_modules/homebridge-hue requires a HomeBridge version of ^0.4.46 which does not satisfy the current HomeBridge version of 0.4.45. You may need to upgrade your installation of HomeBridge.

Any docker update soon?
 
Thanks and keep up the good work!
Tschuki

Build Triggered, Should be done soon, try clicking on force update

Sent from my Pixel 3 using Tapatalk

Hi know you have not made H265ize but do any know a way too update the H265 version it a old one in use

49 minutes ago, tola5 said:

Hi know you have not made H265ize but do any know a way too update the H265 version it a old one in use

I cannot do that as I am not the developer of H265ize

I think the maintainer of the docker CAN update the version of h265ize that is currently available inside the docker if that's what you're asking and I think you are....

So h265ize is supposed to be a set and forget tool - however, once it's process whatever is in the input folder, the docker container stops.  Is this by design?  I'm wanting it to keep tabs on a directory for incoming files and it won't work in it's current form - I might have to use a VM instead which would be a shame.

 

Thanks.