[support] Siwat's Docker Repository


Recommended Posts

Excuse the newb question.  I installed the docker for homebridgewithgui, added the packages as per the doco for the stuff I have (sonoff, garadget, roku etc), it installed the docker, but what port does it run on ?  docker allocations shows this :

HomeBridgewithwebGUIhost    192.168.1.7   ???

Was I supposed to pass in a variable for the host port to access the gui ?

Link to comment
Excuse the newb question.  I installed the docker for homebridgewithgui, added the packages as per the doco for the stuff I have (sonoff, garadget, roku etc), it installed the docker, but what port does it run on ?  docker allocations shows this :
HomeBridgewithwebGUIhost    192.168.1.7   ???
Was I supposed to pass in a variable for the host port to access the gui ?
The default port is 8124ccaf78e89b77bb4d384e434f5da9ac67.jpg

Sent from my Pixel 3 using Tapatalk

Link to comment

ok - looks like this is not a port issue, as the docker dies shortly after starting.

 

Logs say :

 

npm WARN [email protected] requires a peer of chai@>= 2.1.2 < 5 but none was installed.
npm ERR! Linux 4.18.17-unRAID
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "--unsafe-perm" "homebridge-pilight" "homebridge-info" "homebridge-wemo" "homebridge-roku" "homebridge-weather-plus" "homebridge-foscam-nextlevel" "homebridge-sonoff" "homebridge-music" "homebridge-xiaomi-roborock-vacuum" "homebridge-broadband" "homebridge-yamaha-home" "homebridge-ewelink-max" "homebridge-openhab2" "homebridge-apple-tv" "homebridge-konkeplatform" "homebridge-lifx-lan" "homebridge-ewelink-plus" "homebridge-garadget"
npm ERR! node v8.10.0
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE

npm ERR! [email protected] preinstall: `node install.js --preinstall`
npm ERR! Exit status 1


npm ERR! Failed at the [email protected] preinstall script 'node install.js --preinstall'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sodium package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js --preinstall
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs sodium
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls sodium
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /npm-debug.log

Link to comment
On 12/13/2018 at 1:31 PM, vw-kombi said:

ok - looks like this is not a port issue, as the docker dies shortly after starting.

 

Logs say :

 

npm WARN [email protected] requires a peer of chai@>= 2.1.2 < 5 but none was installed.
npm ERR! Linux 4.18.17-unRAID
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "--unsafe-perm" "homebridge-pilight" "homebridge-info" "homebridge-wemo" "homebridge-roku" "homebridge-weather-plus" "homebridge-foscam-nextlevel" "homebridge-sonoff" "homebridge-music" "homebridge-xiaomi-roborock-vacuum" "homebridge-broadband" "homebridge-yamaha-home" "homebridge-ewelink-max" "homebridge-openhab2" "homebridge-apple-tv" "homebridge-konkeplatform" "homebridge-lifx-lan" "homebridge-ewelink-plus" "homebridge-garadget"
npm ERR! node v8.10.0
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE

npm ERR! [email protected] preinstall: `node install.js --preinstall`
npm ERR! Exit status 1


npm ERR! Failed at the [email protected] preinstall script 'node install.js --preinstall'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sodium package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js --preinstall
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs sodium
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls sodium
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /npm-debug.log

add "chai" to aptpackages

Link to comment
12 hours ago, cadaldoo said:

How do I get Phlex working with nginx? ie I'd like it accessible from mydomain.com/phlex or phlex.mydomain.com

 

I have all my other containers accessible in this way but can't quite figure out how to do it for Phlex. I've searched everywhere and I feel like I'm missing something obvious.

You need to edit the public address in setting to reflect your external domain name

Link to comment
On 12/11/2018 at 5:46 AM, Siwat2545 said:

Ok you can try to install manually by downloading the zip file and paste it in the nextcloud's app directory, I'll give you a detailed instructions if you can't do it when I'm done working

 


Sent from my Pixel 3 using Tapatalk
 

 

ANy chance you would be able to give detailed instructions on how to do this? I've been trying to set the config inside the NextCloud container, but it doesn't seem to save anything for me.

Link to comment
7 hours ago, Coolsaber57 said:

ANy chance you would be able to give detailed instructions on how to do this? I've been trying to set the config inside the NextCloud container, but it doesn't seem to save anything for me.

 

Can I see the part where your're having problem? (A screenshot of the config and the app)

Link to comment
On 12/16/2018 at 4:27 PM, Siwat2545 said:

add "chai" to aptpackages

Hi,

OK, added this, start docker, and it seemed to be doing loads of stuff in the log for the docker on startup, but eventually crashed asgain, and the log shows this below :

Thanks

 

npm ERR! Linux 4.18.20-unRAID
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "--unsafe-perm" "homebridge-pilight" "homebridge-info" "homebridge-wemo" "homebridge-roku" "homebridge-weather-plus" "homebridge-foscam-nextlevel" "homebridge-sonoff" "homebridge-music" "homebridge-xiaomi-roborock-vacuum" "homebridge-broadband" "homebridge-yamaha-home" "homebridge-ewelink-max" "homebridge-openhab2" "homebridge-apple-tv" "homebridge-konkeplatform" "homebridge-lifx-lan" "homebridge-ewelink-plus" "homebridge-garadget"
npm ERR! node v8.10.0
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE

npm ERR! [email protected] preinstall: `node install.js --preinstall`
npm ERR! Exit status 1


npm ERR! Failed at the [email protected] preinstall script 'node install.js --preinstall'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sodium package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js --preinstall
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs sodium
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls sodium
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /npm-debug.log

Link to comment

Can you try to pinpoint what package is causing the issue by removing it one at a time?

Hi,
OK, added this, start docker, and it seemed to be doing loads of stuff in the log for the docker on startup, but eventually crashed asgain, and the log shows this below :
Thanks
 
npm ERR! Linux 4.18.20-unRAID
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "--unsafe-perm" "homebridge-pilight" "homebridge-info" "homebridge-wemo" "homebridge-roku" "homebridge-weather-plus" "homebridge-foscam-nextlevel" "homebridge-sonoff" "homebridge-music" "homebridge-xiaomi-roborock-vacuum" "homebridge-broadband" "homebridge-yamaha-home" "homebridge-ewelink-max" "homebridge-openhab2" "homebridge-apple-tv" "homebridge-konkeplatform" "homebridge-lifx-lan" "homebridge-ewelink-plus" "homebridge-garadget"
npm ERR! node v8.10.0
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE

npm ERR! [email protected] preinstall: `node install.js --preinstall`
npm ERR! Exit status 1


npm ERR! Failed at the [email protected] preinstall script 'node install.js --preinstall'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sodium package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js --preinstall
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs sodium
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls sodium
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /npm-debug.log


Sent from my Pixel 3 using Tapatalk

Link to comment
On 12/18/2018 at 1:23 AM, Siwat2545 said:

 

Can I see the part where your're having problem? (A screenshot of the config and the app)

I installed "onlyoffice" app in the NextCloud UI, and I'm confused as to what should go here: image.thumb.png.2265fcd043b771a61bbef85996d45035.png

 

I tried to port forward the docs server, but I'm not sure if I did it correctly.  If you have an example proxy.conf (or just the nginx config for onlyoffice) that would help me double check.

 

Are these supposed to be my internal IP addresses? Or should they be the public-facing web addresses?

 

Or is this not  the way I'm supposed to configure the integration between NextCloud and OnlyOffice?

Link to comment
On 12/19/2018 at 10:20 PM, Siwat2545 said:

Onlyoffice must be exposed to the public address, if your nextcloud use https, onlyoffice must also have https, all field must be point to your document server

When you say onlyoffice must also have https, is it sufficient to have it behind the same reverse proxy (i.e. letsencrypt container) or do I need to set up https in the onlyoffice config itself?  I didn't see any sample proxy config files for onlyoffice in the letsencrypt container, so I made a basic one, but it's not working - is there any trick to getting it working?

 

Also, I keep seeing references to running "set_configuration.sh" bash script in other guides - do you need to do that here? 

Link to comment
When you say onlyoffice must also have https, is it sufficient to have it behind the same reverse proxy (i.e. letsencrypt container) or do I need to set up https in the onlyoffice config itself?  I didn't see any sample proxy config files for onlyoffice in the letsencrypt container, so I made a basic one, but it's not working - is there any trick to getting it working?
 
Also, I keep seeing references to running "set_configuration.sh" bash script in other guides - do you need to do that here? 
You need to set https in onlyoffice itself then you can proxy it through nginx because if you do not set up https in onlyoffice, onlyoffice will rewrite https to http and that will fail

Sent from my Pixel 3 using Tapatalk

Link to comment
5 minutes ago, Siwat2545 said:

You need to set https in onlyoffice itself then you can proxy it through nginx because if you do not set up https in onlyoffice, onlyoffice will rewrite https to http and that will fail

Sent from my Pixel 3 using Tapatalk
 

Dumb question, but how do you set https in onlyoffice for the doc server? there's no GUI config/admin page right? Do you just mean to point it to the https port?

Link to comment
On 12/21/2018 at 8:55 PM, Siwat2545 said:

Sorry for the late reply, I'm haveing a midterm test rn, cert file can be found in the certs directory of your let's encrypt container

Thanks for all your help - and good luck on your midterm!

 

Apologies for bugging you about this, I'm just trying to get this set up, and there's no rush as I'm sure you're still busy.  I don't know if the issue is my reverse proxy config, which is based off of how I saw how the other containers were connecting:

 

# 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 http://$upstream_docs:443;
    }
}

or some issue with the config of the OnlyOfficeDocumentServer config.  

 

When I access via the internal IP, I get a Cert error for both the http (tells me my certs are only for my sub-domains) and https (shows as "self-signed") WebUIs URLs, but I can add an exception and get to the page.  When I attempt to access the docs server via the external subdomain, I get a 502 error (I'm not sure what I'm supposed to get - perhaps a "document server is running" page?).

 

Any advice? Is there a better example of how I should be proxying the doc server?

Edited by Coolsaber57
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.