[support] Siwat's Docker Repository


435 posts in this topic Last Reply

Recommended Posts

  • Replies 434
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Yeah i have the same. I havent had time to look into this as yet but a quick fix is roll back to the earlier container. In the template change repository to add :6.0 on the end so onlyoffice/

I had quite a bit of trouble getting OnlyOfficeDocumentServer to work with nextcloud and letsencrypt. So I had letsencrypt install for plex etc and got it working with nextcloud. The confusing part of

These instructions should be stickied! THANK YOU!

Posted Images

I have some problems with the Onlyoffice container, i run it first stock from template and was getting MySQL errors, i then changed to an external mariadb instance and this error is gone. But now i getting errors related to elasticsearch, i would use an external there too but there are no variables for that. 

 

more infos are here https://github.com/ONLYOFFICE/Docker-CommunityServer/issues/100 , i created a github issue becouse i think its more related to the docker image than this thread but i hope that someone has the same proble or have a fix for that :) 

Edited by Wuast94
Link to post
On 9/28/2020 at 6:43 PM, xanvincent said:

Is the Adguard Home container working? Console doesn't work (just a black screen) and WebGUI doesn't load. I don't see anything created in the conf directory either.

Yes i got is working today if you still need some help and can share  some screenshots and tips.

Link to post
  • 3 weeks later...
3 hours ago, MMW said:

If you have some pointers that could be useful.

Hi,just give it fixed IP then check the logs will be some errors because missing a file is some directory.

Then just check where is missing the file and create it manual on the desktop and copy and paste in the directory.

Log in in Adguard only with the IP which you set before dont add :PORT number and make the setup of the Adguard and put the ip in your router DNS and thats it.

I stop using it because i buy Pi 3 and install it there because my server sleep from 23h til 07 and i lose internet connection so Pi runs now 24/7 but for a week the docker on Unraid was working and blocking perfect.

adguard1.png

adguard.png

Edited by Vesko
Link to post
On 5/26/2020 at 5:37 PM, zarfx4 said:

What is the path of the Homebridge Logs within the container?  Does not seem to be /var/log which is what i thought was standard..??..

Did you get this sorted.  I am trying to get log access.  I found a 0byte file /mnt/user/disk/appdata/homebridge/log.txt but nothing obviously written to it?

Link to post
On 10/31/2020 at 12:45 PM, Vesko said:

Hi,just give it fixed IP then check the logs will be some errors because missing a file is some directory.

Then just check where is missing the file and create it manual on the desktop and copy and paste in the directory.

Log in in Adguard only with the IP which you set before dont add :PORT number and make the setup of the Adguard and put the ip in your router DNS and thats it.

I stop using it because i buy Pi 3 and install it there because my server sleep from 23h til 07 and i lose internet connection so Pi runs now 24/7 but for a week the docker on Unraid was working and blocking perfect.

adguard1.png

adguard.png

I have given it a IP. The only things I see in the log is:

Nov  9 18:08:58 dragon nginx: 2020/11/09 18:08:58 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:08:58 dragon nginx: 2020/11/09 18:08:58 [error] 25696#25696: *7273 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7276 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7280 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"
Nov  9 18:09:00 dragon nginx: 2020/11/09 18:09:00 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:09:00 dragon nginx: 2020/11/09 18:09:00 [error] 25696#25696: *7284 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"

Any ideas?

Link to post
3 hours ago, CountRock said:

I have given it a IP. The only things I see in the log is:


Nov  9 18:08:58 dragon nginx: 2020/11/09 18:08:58 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:08:58 dragon nginx: 2020/11/09 18:08:58 [error] 25696#25696: *7273 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7276 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7280 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"
Nov  9 18:09:00 dragon nginx: 2020/11/09 18:09:00 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:09:00 dragon nginx: 2020/11/09 18:09:00 [error] 25696#25696: *7284 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"

Any ideas?

What’s at 192.168.1.202 and 192.168.1.112?

Link to post
18 hours ago, CountRock said:

I have given it a IP. The only things I see in the log is:


Nov  9 18:08:58 dragon nginx: 2020/11/09 18:08:58 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:08:58 dragon nginx: 2020/11/09 18:08:58 [error] 25696#25696: *7273 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7276 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:08:59 dragon nginx: 2020/11/09 18:08:59 [error] 25696#25696: *7280 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"
Nov  9 18:09:00 dragon nginx: 2020/11/09 18:09:00 [error] 25696#25696: *7253 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/token HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/token", host: "192.168.1.202", referrer: "http://192.168.1.202/dockerterminal/AdGuard-Home/"
Nov  9 18:09:00 dragon nginx: 2020/11/09 18:09:00 [error] 25696#25696: *7284 connect() to unix:/var/tmp/AdGuard-Home.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.112, server: , request: "GET /dockerterminal/AdGuard-Home/ws HTTP/1.1", upstream: "http://unix:/var/tmp/AdGuard-Home.sock:/ws", host: "192.168.1.202"

Any ideas?

Today i install it on my new installed Unraid and no just works straight away just give it fixed IP and done i think is updated or something.

 Try to uninstall the docker Adguarg then go to Appdata folder and delete the folder Adguard and then install it again and only fill up the ip before pull down the container.Open the logs and look for the last line just copy and paste in browser and should work.add.thumb.png.e91ab3c0f833e8a8a0bc94afb01c111f.png 

ad.png

Link to post
3 hours ago, CountRock said:

I just installed it yesterday for the first time. 202 is my Unraid server and 112 was the laptop I was using to access the GUI.

Delete everything how i explain in previous post and install again and will be fine.If 202 is your unraid IP then give another IP 200 maybe to Adguard dont give same IP to the docker.

Edited by Vesko
Link to post
  • 4 weeks later...

Hello.  I had the OpenOfficeDocumentServer working well until the most recent update.  Now I cannot connect. Not sure what changed. Using reverse proxy through SWAG.  When I try to hit it via command-line, here's what I get:

 

wget https://docserver.myserver.org

 

--2020-12-05 11:55:55-- https://docserver.myserver.org/
Resolving docserver.myserver.org (docserver.myserver.org)... xxx.xxx.xx.xx
Connecting to docserver.myserver.org (docserver.myserver.org)|xxx.xxx.xx.xx|:443... connected.
HTTP request sent, awaiting response... 400 Bad Request
2020-12-05 11:55:55 ERROR 400: Bad Request.

 

Been googling around.  Tried reinstalling container.  Copying over the key files again.  Restarted SWAG.  Same result.  Document Server was working perfectly before the update and its error logs are empty.  SWAG's error logs don't seem to show any problems with the document server access.

 

Any ideas out there?

 

UPDATE:

Getting this error too, but unsure if its related...

 

image.thumb.png.9ae78e7a31fc15b9224264421b3110ad.png

 

Not sure what this is referring to...

Edited by akshunj
adding info
Link to post
1 hour ago, akshunj said:

Hello.  I had the OpenOfficeDocumentServer working well until the most recent update.  Now I cannot connect. Not sure what changed. Using reverse proxy through SWAG.  When I try to hit it via command-line, here's what I get:

 

wget https://docserver.myserver.org

 

--2020-12-05 11:55:55-- https://docserver.myserver.org/
Resolving docserver.myserver.org (docserver.myserver.org)... xxx.xxx.xx.xx
Connecting to docserver.myserver.org (docserver.myserver.org)|xxx.xxx.xx.xx|:443... connected.
HTTP request sent, awaiting response... 400 Bad Request
2020-12-05 11:55:55 ERROR 400: Bad Request.

 

Been googling around.  Tried reinstalling container.  Copying over the key files again.  Restarted SWAG.  Same result.  Document Server was working perfectly before the update and its error logs are empty.  SWAG's error logs don't seem to show any problems with the document server access.

 

Any ideas out there?

 

Yeah i have the same. I havent had time to look into this as yet but a quick fix is roll back to the earlier container.

In the template change repository to add :6.0 on the end so

onlyoffice/documentserver:6.0

 

  • Like 3
  • Thanks 4
Link to post
23 minutes ago, SpaceInvaderOne said:

Yeah i have the same. I havent had time to look into this as yet but a quick fix is roll back to the earlier container.

In the template change repository to add :6.0 on the end so


onlyoffice/documentserver:6.0

 

Life saver!  Thanks, man!

Link to post
On 12/5/2020 at 1:17 PM, SpaceInvaderOne said:

Yeah i have the same. I havent had time to look into this as yet but a quick fix is roll back to the earlier container.

In the template change repository to add :6.0 on the end so


onlyoffice/documentserver:6.0

 

+1 on the Life Saver!!!  Appreciate everything you do.  Was pulling my hair out trying to figure out what happened and why it was no longer working.  Rolling back got me back up and running. 

Link to post
4 minutes ago, gzibell said:

+1 on the Life Saver!!!  Appreciate everything you do.  Was pulling my hair out trying to figure out what happened and why it was no longer working.  Rolling back got me back up and running. 

Interesting I’ll look into this when I’m free.

Link to post
On 12/5/2020 at 3:17 PM, SpaceInvaderOne said:

Yeah i have the same. I havent had time to look into this as yet but a quick fix is roll back to the earlier container.

In the template change repository to add :6.0 on the end so


onlyoffice/documentserver:6.0

 

Thanks so much Spaceinvader.   Life saver to say the least.   I had thing a few months ago up and running with the old only office docker from only office but noted things not working(don't use much of document editing so probably had been down for a while.).  But last night trying to find a new docker came across Siwats registry with your comment so downloaded it.  Couldn't get it working until I found your comment. 

 

On 12/7/2020 at 12:45 PM, Siwat2545 said:

Interesting I’ll look into this when I’m free.

And thanks Siwat for looking into what happened.  !!!

Also sorry for a stupid question,  I had followed Spaceinvaders video for integration with Nextcloud and noticed that in the cert folder there is an extra file .csr .     wondering if anyone can help me understand if this is needed? (I copied over the .crt and .key files from SWAG as per spaceinvaders video... 

 

Link to post
21 minutes ago, Aceriz said:

Thanks so much Spaceinvader.   Life saver to say the least.   I had thing a few months ago up and running with the old only office docker from only office but noted things not working(don't use much of document editing so probably had been down for a while.).  But last night trying to find a new docker came across Siwats registry with your comment so downloaded it.  Couldn't get it working until I found your comment. 

 

And thanks Siwat for looking into what happened.  !!!

Also sorry for a stupid question,  I had followed Spaceinvaders video for integration with Nextcloud and noticed that in the cert folder there is an extra file .csr .     wondering if anyone can help me understand if this is needed? (I copied over the .crt and .key files from SWAG as per spaceinvaders video... 

 

My server broke so yeaaaa it’s gonna take a while.

Edited by Siwat2545
Link to post

Looks like if you're on the Nextcloud stable channel, update to 20.0.4 is available.  Also, the internal onlyoffice nextcloud app/plugin is updated to 6.2.0.  Anyone know if this fixes the onlyoffice container issues?  Going to take the plunge while on vacation next week.

Link to post
9 hours ago, akshunj said:

Looks like if you're on the Nextcloud stable channel, update to 20.0.4 is available.  Also, the internal onlyoffice nextcloud app/plugin is updated to 6.2.0.  Anyone know if this fixes the onlyoffice container issues?  Going to take the plunge while on vacation next week.

I took that plunge. Didn't help so I found myself here. Rolling back to 6.0 also didn't help (also tried 6.0.2, 6.0.2.5 & 6.0.1). This doesn't make much sense because it was working before updates. Nothing else has been done to the docker.

 

When I wget the doc server I get an HTTP 400, typing in the local ip & port manual or going to the web ui returns nothing.  This is the only errors I see in the logs:

 

==> /var/log/onlyoffice/documentserver/docservice/out.log <==
[2020-12-19T18:44:38.570] [WARN] nodeJS - Express server listening on port 8000 in production-linux mode
[2020-12-19T18:45:25.833] [WARN] nodeJS - Express server starting...
[2020-12-19T18:45:25.837] [WARN] nodeJS - Failed to subscribe to plugin folder updates. When changing the list of plugins, you must restart the server. https://nodejs.org/docs/latest/api/fs.html#fs_availability

[2020-12-19T18:45:25.950] [WARN] nodeJS - Express server listening on port 8000 in production-linux mode
[2020-12-19T18:58:20.993] [WARN] nodeJS - Express server starting...
[2020-12-19T18:58:20.999] [WARN] nodeJS - Failed to subscribe to plugin folder updates. When changing the list of plugins, you must restart the server. https://nodejs.org/docs/latest/api/fs.html#fs_availability

[2020-12-19T18:58:21.599] [WARN] nodeJS - Express server listening on port 8000 in production-linux mode
[2020-12-19T18:59:07.729] [WARN] nodeJS - Express server starting...
[2020-12-19T18:59:07.732] [WARN] nodeJS - Failed to subscribe to plugin folder updates. When changing the list of plugins, you must restart the server. https://nodejs.org/docs/latest/api/fs.html#fs_availability

But per this post this message is normal. https://github.com/ONLYOFFICE/DocumentServer/issues/1004#issuecomment-700654979 

 

Also worth noting that I have two separate servers both of which have the same issue, both broke likely due to the update as one server wasn't touched at all and the other had only minor unrelated changes between the doc server working and not, and neither work after rollback. Logs remain unchanged.

Edited by TheWhiteKnyt
Link to post

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.