[support] Siwat's Docker Repository


Recommended Posts

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

Link to comment
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 by Coolsaber57
  • Like 1
Link to comment
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.

Link to comment
  • 2 weeks later...
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?

Link to comment
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...

 

Link to comment
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

Link to comment
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

Link to comment
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

Link to comment
  • 2 weeks later...

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

Link to comment
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

Link to comment

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.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.