[support] Siwat's Docker Repository

[zarkoff]

Hi @Siwat2545,

 

First, thank you for the Adguard-home repository.

 

But I've a question: the docker now says "not available".

 

I'm a beginner, so I don't know if this is something I've to do on my side or if this is something to be maintained on your side or something else ?

 

 

Thank you.

 

Zarkoff

[JonathanM]

9 hours ago, zarkoff said:

I've a question: the docker now says "not available".

 

[zarkoff]

@JonathanM Oh thank you. It worked after installing the patch and a rebooting.

Edited February 17, 2023 by zarkoff

[Tweak91]

humhub how do i change upload size ? 

[Jameszy]

Edit: Problem Solved.

 

Changed interface from br0 to Bridge to share the same ip address as the unraid machine, added port forwarding for port 80 container side to 81 host side...  Service still accessible from the LAN, service accessible from unraid... BOOM works!

 

 

Greetings!

I have installed the adguard docker container and Im having an interesting problem.

I am unable to query the dns server from outside the container on my local machine,
but it works fine from everywhere else...

 

Unraid

root@NAS:~# nslookup
> apple.com
Server:         192.168.1.7
Address:        192.168.1.7#53

Non-authoritative answer:
Name:   apple.com
Address: 17.253.144.10
Name:   apple.com
Address: 2620:149:af0::10

> server 192.168.1.130
Default server: 192.168.1.130
Address: 192.168.1.130#53

> apple.com
;; communications error to 192.168.1.130#53: timed out
;; communications error to 192.168.1.130#53: timed out
;; communications error to 192.168.1.130#53: timed out
;; no servers could be reached

Nitrogen (Another Linux box on my network)

[ jameszy@nitrogen: ~ ] Sat Mar 11 11:11:19
$ nslookup

> server 192.168.1.7
Default server: 192.168.1.7
Address: 192.168.1.7#53
> apple.com
Server:        192.168.1.7
Address:    192.168.1.7#53

Non-authoritative answer:
Name:    apple.com
Address: 17.253.144.10
Name:    apple.com
Address: 2620:149:af0::10

> server 192.168.1.130
Default server: 192.168.1.130
Address: 192.168.1.130#53

> apple.com
Server:        192.168.1.130
Address:    192.168.1.130#53

Non-authoritative answer:
Name:    apple.com
Address: 17.253.144.10
Name:    apple.com
Address: 2620:149:af0::10

So the problem is traffic cant traverse from unraid to the docker container, but traffic is not impeded from external sources to the docker container or to the bare metal unraid machine.

 

I dont see any weird iptables rules, or odd route output... Docker containers are kind of confusing to me so im not sure where to start with troubleshooting..

 

Thanks!

 

Edited March 11, 2023 by Jameszy
Solved Issue

[nerbonne]

Can anyone tell me how to get a command to run when ubuntu playground starts?  I've messed around with it a bit, but it's pretty frustrating because every time you change the config it reloads and wipes all the data.  I'm trying to execute this command on container start: 

 

/hpool-miner-chia-linux-amd64 > /dev/null 2>&1 &

 

[Stubbs]

I am just not understanding this container. I don't know why it can't be as straight-forward as others.

 

I have functioning domains for Jellyfin, Ombi and Nextcloud, but for some reason OnlyOffice will not work. I am still stuck on 

"502 Bad Gateway - nginx" when I open it in a web browser.

 

As per the instructions in this post:

 

On 11/15/2022 at 2:52 PM, Wong said:

 

Just a record for anyone in the future encounter similar issue as me. I manage to solve it.

Step 1: Remove the existing onlyoffice docker and it's image. Make sure to also delete onlyoffice file inside the appdata share.

Step 2: Reinstall the onlyoffice docker. As of 15/11/2022, the docker template had one small issue. Credit to @eyesfit. Please edit the Database path as shown in below. 

 

Step 3: Remember to save or edit your secret keys. Then click apply.

Step 4: Copy your cert.crt, cert.key and fullchain.pem from your nginx manager or swag to the /mnt/user/appdata/onlyofficeds/Data. Do not create a cert folder and put in there. This will cause your OnlyOffice to failed to start due to nginx config error.

Step 5: Rename your cert.crt to onlyoffice.crt , cert.key to onlyoffice.key , fullchain.pem to dhparam.pem .

Step 6: Do not follow the Spaceinvader video regarding the nginx template. Use the latest documentserver template in your nginx manager or swag. And adjust accordingly to your domain.

Step 7: Restart docker for everything related. DONE! you good to go with the latest version. 

 

Please give a like my comment if it help you! thanks

 

I removed the container and the appdata folder.

I re-installed it and added that database path (which wasn't even there before). I changed the secret key to something generated.

I ran:

root@UnraidServer:~# cp /mnt/user/appdata/swag/keys/cert.crt /mnt/user/appdata/onlyofficeds/Data/certs/onlyoffice.crt
root@UnraidServer:~# cp /mnt/user/appdata/swag/keys/cert.key /mnt/user/appdata/onlyofficeds/Data/certs/onlyoffice.key
root@UnraidServer:~# cp /mnt/user/appdata/swag/keys/letsencrypt/fullchain.pem /mnt/user/appdata/onlyofficeds/Data/certs/dhparam.pem

 

Which copies and renames the necessary reverse proxy files for this container.

I am using the documentserver subdomain config from within the Swag container.

I renamed the "OnlyOfficeDocumentServer" container to "documentserver" as per the instructions in the swag subdomain template.

I added a CNAME called documentserver in my registrar's DNS settings.

I restarted both the documentserver and swag containers.

 

But it still doesn't work. I keep getting the old "502 Bad Gateway".

Edited April 24, 2023 by Stubbs

[profzelonka]

Please advise - For the HumHub docker, is it safe to update humhub manually within the docker or is it better to wait for the docker to be updated instead?

[bigbangus]

I've got a weird issue. The health check for ONLYOFFICE config is good in the Nextcloud > Admin Settings > OnlyOffice > Server Settings

 

but whenever I try to click on a Document in Nextcloud to start editing, I get this:

 

Can anyone point me to the relevant logs or how to start diagnosing this?

[bigbangus]

Crickets. Can anyone help with this issue.  I tried reaching to OO for support and they said Unraid not supported  which I think means they just don't understand Unraid is linux + dockers.

 

https://forum.onlyoffice.com/t/nextcloud-server-settings-pass-but-cant-open-document/4961/7

 

Maybe someone could share a working nginx proxy-conf with me. Here is what I have 

 

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

    server_name onlyoffice.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {

        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app OnlyOfficeDocumentServer;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_max_temp_file_size 2048m;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }
}

 

Healthcheck in nextcloud is true, but then opening any document I get "onlyoffice.xxx.xx refuses to connect"

Edited June 7, 2023 by bigbangus

[Joedy]

Are you going to release an Axigen X5 docker or how would I upgrade my current to this please?

[Kwebber321]

Recently i got a new router which caused my server to get a new ip address. I couldn't reserve the previous address on the new server since that address wasnt available in the pool. previously it was 192.168.1.25 and i had adguard installed and running. Now my address is 192.168.0.237. when i install adguard and try to launch the web ui, it just hangs and i get the connection timed out. I tried selecting a random address in the ip pool in my router but that got me the same result. also when i open the console, i get this message spammed over and over again.

 

OCI runtime exec failed: exec failed: unable to start container process: exec: "bash": executable file not found in $PATH: unknown adguard

 

removing the container and reinstalling dosent work as i keep getting the same result over and over again and im not sure what to do.

Edited July 3, 2023 by Kwebber321

[Dekel]

Since 6.12 AdGuard Home is not working, No matter what I try bridge, Host, custom bridge it simply either wont start or fail to route the traffic to the container.

 

Any solution?

 

Dekel

[jfoxwoosh]

On 5/24/2023 at 1:04 PM, bigbangus said:

I've got a weird issue. The health check for ONLYOFFICE config is good in the Nextcloud > Admin Settings > OnlyOffice > Server Settings

 

but whenever I try to click on a Document in Nextcloud to start editing, I get this:

 

Can anyone point me to the relevant logs or how to start diagnosing this?

+1,  I am having this problem as well.

As far as I can tell, documentserver is working correctly. I can access through reverse proxy, and the example editor test works just fine. The nextcloud's onlyoffice plugin can connect to the document server. However, nextcloud can no longer open any of the office files within the browser. Using Edge/Chrome will result in the same error message "refused to connect." Using firefox will either show a blank page, or a warning message saying it cannot open an already embedded page within the tab.

[bigbangus]

On 7/5/2023 at 9:23 PM, jfoxwu said:

+1,  I am having this problem as well.

As far as I can tell, documentserver is working correctly. I can access through reverse proxy, and the example editor test works just fine. The nextcloud's onlyoffice plugin can connect to the document server. However, nextcloud can no longer open any of the office files within the browser. Using Edge/Chrome will result in the same error message "refused to connect." Using firefox will either show a blank page, or a warning message saying it cannot open an already embedded page within the tab.

 

So I managed to solve the issue. I believe I had a combination of errors in my swag nginx config files. I returned all my swag nginx configs back to default (ssl.conf, proxy.conf, resolver.conf, nginx.conf).

 

Also here is my onlyoffice proxy-conf

  GNU nano 7.2                                                                                             onlyoffice.subdomain.conf                                                                                                        
## Version 2023/05/31
# make sure that your onlyoffice documentserver container is named documentserver
# make sure that your dns has a cname set for documentserver

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

    server_name onlyoffice.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {

        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app OnlyOfficeDocumentServer;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        #proxy_redirect off;
    }
}

 

And finally, delete all your browser cache and restart your browser. Also after trying to open a document in nextcloud, if you still get a refuse to connect, do a Ctrl+Shift+R and it may work. This was my major problem. I had solved the issue but kept going back because my browser cache was all jacked up.

 

Hope it works, let me know.

Edited July 12, 2023 by bigbangus

[jfoxwoosh]

@bigbangus

I checked my reverse proxy conf file and noticed the default from swag's documentserver proxy conf template uses http/Port80 instead of https/Port443. I changed it to https and 443 just like yours and clear the cache of my browser. After restarting swag, I can access documentserver from my public domain url just fine. However, I am still suffering the same issue.

 

No idea what is going on. For now I have setup up Collabora. Will revisit this if there is new update to either documentserver or the onlyoffice nextcloud plug in.

[bigbangus]

8 minutes ago, jfoxwu said:

@bigbangus

I checked my reverse proxy conf file and noticed the default from swag's documentserver proxy conf template uses http/Port80 instead of https/Port443. I changed it to https and 443 just like yours and clear the cache of my browser. After restarting swag, I can access documentserver from my public domain url just fine. However, I am still suffering the same issue.

 

No idea what is going on. For now I have setup up Collabora. Will revisit this if there is new update to either documentserver or the onlyoffice nextcloud plug in.

what do you mean exactly still suffering the same issue while still being able to hit it fine from your public domain url?

 

also what have you configured in the Nextcloud ONLYOFFICE settings for urls?

Edited July 12, 2023 by bigbangus

[jfoxwoosh]

@bigbangus

2 minutes ago, bigbangus said:

what do you mean exactly still suffering the same issue while still being able to hit it fine from your public domain url?

I can see documentserver's welcome page from its subdomain url.

 

Here is the update. If I revert the ssl.conf to swag's initial template state, then my onlyoffice works again. However, the only changes I made are in accordance to swag nextcloud's proxy template so to pass the nextcloud's security check (e.g. enabling add_header X-Frame-Options..., etc.). How do you deal with this?

[bigbangus]

1 hour ago, jfoxwu said:

However, the only changes I made are in accordance to swag nextcloud's proxy template so to pass the nextcloud's security check (e.g. enabling add_header X-Frame-Options..., etc.). How do you deal with this?

 

You add them to the nextcloud proxy-conf in swag. Here is what mine looks like with all the comments removed:

 

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

    server_name nextcloud.*;

    add_header Strict-Transport-Security "max-age=15768000; includeSubdomains; preload;";

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app nextcloud;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_buffering off;
        proxy_max_temp_file_size 2048m;
    }
}

 

and then make sure your proxy.conf which is referenced above is back to default in swag as such:

                                                                                             
## Version 2023/02/09 - Changelog: https://github.com/linuxserver/docker-swag/commits/master/root/defaults/nginx/proxy.conf.sample

# Timeout if the real server is dead
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;

# Proxy Connection Settings
proxy_buffers 32 4k;
proxy_connect_timeout 240;
proxy_headers_hash_bucket_size 128;
proxy_headers_hash_max_size 1024;
proxy_http_version 1.1;
proxy_read_timeout 240;
proxy_redirect http:// $scheme://;
proxy_send_timeout 240;

# Proxy Cache and Cookie Settings
proxy_cache_bypass $cookie_session;
#proxy_cookie_path / "/; Secure"; # enable at your own risk, may break certain apps
proxy_no_cache $cookie_session;

# Proxy Header Settings
proxy_set_header Connection $connection_upgrade;
proxy_set_header Early-Data $ssl_early_data;
proxy_set_header Host $host;
proxy_set_header Proxy "";
proxy_set_header Upgrade $http_upgrade;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Method $request_method;
proxy_set_header X-Forwarded-Port $server_port;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-Ssl on;
proxy_set_header X-Forwarded-Uri $request_uri;
proxy_set_header X-Original-Method $request_method;
proxy_set_header X-Original-URL $scheme://$http_host$request_uri;
proxy_set_header X-Real-IP $remote_addr;

 

 

 

Edited July 12, 2023 by bigbangus

[jfoxwoosh]

Don't really understand all these personally, so I just did some trials and errors. I found out it is when "add_header X-Frame-Options "SAMEORIGIN" always" is enabled in ssl.conf that will break the integration between nextcloud and onlyoffice.

 

Upon further reading, this seems to be the expected behavior.

https://forum.onlyoffice.com/t/error-message-when-opening-creating-a-document-from-update/4392/12

 

For anyone using swag and its template for nextcloud reverse proxy, comment out "proxy_hide_header X-Frame-Options" in the template so to pass nextcloud's security test as suggested in nextcloud's github issue #8550. Don't enable it within ssl.conf which will add this header to any proxy conf that calls for this file.

 

# Hide proxy response headers from Nextcloud that conflict with ssl.conf
# Uncomment the Optional additional headers in SWAG's ssl.conf to pass Nextcloud's security scan
proxy_hide_header Referrer-Policy;
proxy_hide_header X-Content-Type-Options;
#proxy_hide_header X-Frame-Options;
proxy_hide_header X-XSS-Protection;

 

[Darksurf]

I cannot get the onlyoffice-document server docker working for the love of me. I cannot understand how we have Dockers which should make this a very turnkey process and it becomes a very NOT turn-key process. I've followed instructions and there just isn't any comprehensive guide to get this nightmare working. I've tried getting both onlyoffice and collabora working, neither of which I could get working. Neither of which seem to have a very good document explaining how to get it up and working as a docker either.

If anyone can break this down for me, I'd appreciate it, because I've fought this for hours and am giving up until someone can explain this to me. I've generated the keys/certs etc but cannot connect on https. nextcloud now requires https for some reason. It feels like someone delivered a produce with some assembly required and no instructions on how to assemble it.

[RickSaysMeh]

I am having an issue getting Nextcloud documents to open via OpenOffice.

 

I use the latest lscr.io/linuxserver/nextcloud Docker container and the latest onlyoffice/documentserver Docker container in UNRAID. I use a physical pfsense firewall with haproxy for reverse proxy and SSL cert. Inside my network, it also has DNS configured so that if anyone goes to the external domain name, it will go to the firewall's IP where haproxy will send it to the correct port on UNRAID.

 

I'm not sure when this broke, but now when I try to open a document, it shows an error saying "Download failed." and looking at the logs for OnlyOffice, I see a nodeJS error due to the DNS resolution for the nextcloud address being a private IP. This is correct for my configuration... Is it possible to allow private IPs for this?

[Runaround]

Any chance we can get a node.js update for the homebridge-gui docker? I have several plugins saying incompatible engine now. There are a few other warn lines.

 

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { homebridge: '>=1.6.0', node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142

 

 

[Siwat2545]

On 8/23/2023 at 9:27 AM, Runaround said:

Any chance we can get a node.js update for the homebridge-gui docker? I have several plugins saying incompatible engine now. There are a few other warn lines.

 

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { homebridge: '>=1.6.0', node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142

Hi! I just updated to NodeJS 18 and Ubuntu 22.04 LTS

 

 

[Runaround]

28 minutes ago, Siwat2545 said:

 

Thanks!