Siwat2545 Posted December 27, 2018 Author Share Posted December 27, 2018 You need to proxy pass to https://(your documentserver url) Quote Link to comment
francrouge Posted December 28, 2018 Share Posted December 28, 2018 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 Quote Link to comment
Siwat2545 Posted December 28, 2018 Author Share Posted December 28, 2018 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 modeYes, this is normal, it will use all the CPU for encoding, I suggest you pin the CPU core to restrict it's usageSent from my Pixel 3 using Tapatalk Quote Link to comment
francrouge Posted December 28, 2018 Share Posted December 28, 2018 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 Quote Link to comment
Coolsaber57 Posted January 3, 2019 Share Posted January 3, 2019 (edited) 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, 2019 by Coolsaber57 1 Quote Link to comment
Siwat2545 Posted January 5, 2019 Author Share Posted January 5, 2019 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. Quote Link to comment
piotrasd Posted January 15, 2019 Share Posted January 15, 2019 Hi please add to you container package iputils-ping as some plugins for home bridge required ping package like homebridge-samsung-tizen Thanks Quote Link to comment
Siwat2545 Posted January 17, 2019 Author Share Posted January 17, 2019 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 Quote Link to comment
ampm-it Posted January 17, 2019 Share Posted January 17, 2019 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. Quote Link to comment
trurl Posted January 17, 2019 Share Posted January 17, 2019 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? Quote Link to comment
ampm-it Posted January 17, 2019 Share Posted January 17, 2019 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... Quote Link to comment
itsdandandan Posted January 18, 2019 Share Posted January 18, 2019 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. Quote Link to comment
Siwat2545 Posted January 19, 2019 Author Share Posted January 19, 2019 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 phlexSent from my Pixel 3 using Tapatalk Quote Link to comment
Siwat2545 Posted January 19, 2019 Author Share Posted January 19, 2019 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_KEYValue: [Your API Key]Sent from my Pixel 3 using Tapatalk Quote Link to comment
itsdandandan Posted January 20, 2019 Share Posted January 20, 2019 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? Quote Link to comment
Siwat2545 Posted January 20, 2019 Author Share Posted January 20, 2019 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]:443Note that the url is https as Google and Alexa won't accept http unencryptedSent from my Pixel 3 using Tapatalk Quote Link to comment
Siwat2545 Posted January 20, 2019 Author Share Posted January 20, 2019 I have it working with subdomain, in the config of phlex, enter https://[yoursubdomain]:443Note that the url is https as Google and Alexa won't accept http unencryptedSent from my Pixel 3 using Tapatalk Here's my configSent from my Pixel 3 using Tapatalk Quote Link to comment
itsdandandan Posted January 20, 2019 Share Posted January 20, 2019 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) Quote Link to comment
Siwat2545 Posted January 20, 2019 Author Share Posted January 20, 2019 4 hours ago, itsdandandan said: Apologies, I meant the nginx config (if you are using nginx) I'm actually using HAProxy, sorry Quote Link to comment
Tschuki Posted January 30, 2019 Share Posted January 30, 2019 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 Quote Link to comment
Siwat2545 Posted January 31, 2019 Author Share Posted January 31, 2019 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 updateSent from my Pixel 3 using Tapatalk Quote Link to comment
tola5 Posted February 2, 2019 Share Posted February 2, 2019 Hi know you have not made H265ize but do any know a way too update the H265 version it a old one in use Quote Link to comment
Siwat2545 Posted February 2, 2019 Author Share Posted February 2, 2019 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 Quote Link to comment
Marshalleq Posted February 5, 2019 Share Posted February 5, 2019 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.... Quote Link to comment
Marshalleq Posted February 5, 2019 Share Posted February 5, 2019 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. Quote Link to comment
Recommended Posts
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.