Trying to get adguard up and running using the defaults in the template, it give me the error attached. I have no other dockers using port 53

 

I can run it with network type: custom but I'd rather keep it clean if I can. Running unRAID 6.10 RC2

9 hours ago, Wong said:

 

Error when trying to connect (Not supported version) (version 6.0.2.5)

 

Does anyone have this same error? I not sure when the error started but I just realized it today. It was working fine for me before.

 

 

I got the same issue. It comes from a compatibility issue between the NC oO app and the only office server. You have to manually downgrade the NC app.

 

I don't remember the details but you can find it easily if you google it.

I remember you need to delete the oO folder in nextcloud/app folder, downloads the right version of the only office plugin and untar it there. You might have to reactivate it from nextcloud admin page. Then it works ! You just have to not upgrade it

 

Hope it helps,

Kam

@eatoff @Kam

 

 

On 10/4/2021 at 6:20 AM, ab5g said:

Hi Siwat2545 - I am on Unraid 6.10-RC1 and I get the following error when the container starts. 

It is easily fixed by chmod 640 etc/ssl/private/ssl-cert-snakeoil.key

 

Can you incorporate this into the container image please ?

 

 

2021-10-04 04:10:50.135 UTC [135] FATAL: private key file "/etc/ssl/private/ssl-cert-snakeoil.key" has group or world access 
2021-10-04 04:10:50.135 UTC [135] DETAIL: File must have permissions u=rw (0600) or less if owned by the database user, or permissions u=rw,g=r (0640) or less if owned by root. 
2021-10-04 04:10:50.143 UTC [135] LOG: database system is shut down pg_ctl: could not start server Examine the log output. ...fail! * Starting RabbitMQ Messaging Server rabbitmq-server ...done. Waiting for connection to the localhost host on port 5432 
Waiting for connection to the localhost host on port 5432 
Waiting for connection to the localhost host on port 5432 
Waiting for connection to the localhost host on port 5432 
Waiting for connection to the localhost host on port 5432 
Waiting for connection to the localhost host on port 5432 

 

Hey @ab5g did you found a solution?

Homebridge is in need of an update. 2018? that's quite a while back.
 

I dumbly updated it via the GUI, which ain't gonna work.  And now it doesn't boot.
[12/19/2021, 10:11:45 PM] Failed to save cached accessories to disk: EROFS: read-only file system, open '/root/.homebridge/accessories/cachedAccessories'
/bin/sh: 1: cannot create /root/.homebridge/log.txt: Read-only file system

npm WARN notsup Unsupported engine for [email protected]: wanted: {"homebridge":"^1.3.8","node":"^16.13.1"} (current: {"node":"12.20.1","npm":"6.14.10"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]

37 minutes ago, zaker said:

Homebridge is in need of an update. 2018? that's quite a while back.
 

I dumbly updated it via the GUI, which ain't gonna work.  And now it doesn't boot.
[12/19/2021, 10:11:45 PM] Failed to save cached accessories to disk: EROFS: read-only file system, open '/root/.homebridge/accessories/cachedAccessories'
/bin/sh: 1: cannot create /root/.homebridge/log.txt: Read-only file system

npm WARN notsup Unsupported engine for [email protected]: wanted: {"homebridge":"^1.3.8","node":"^16.13.1"} (current: {"node":"12.20.1","npm":"6.14.10"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]

There seems to be a problem with my jenkins pipeline, should be fixed now.

On 12/2/2021 at 9:33 PM, eatoff said:

Trying to get adguard up and running using the defaults in the template, it give me the error attached. I have no other dockers using port 53

 

I can run it with network type: custom but I'd rather keep it clean if I can. Running unRAID 6.10 RC2

 

I just ran into this issue this morning upon my first run of AdGuardHome.  FOund this on the home page:

 

https://registry.hub.docker.com/r/adguard/adguardhome#resolved-daemon

 

 

3 minutes ago, MrDecepticon said:

 

I just ran into this issue this morning upon my first run of AdGuardHome.  FOund this on the home page:

 

https://registry.hub.docker.com/r/adguard/adguardhome#resolved-daemon

 

 

This error will occur when the container is set to use host or bridge network, you must use brX (br0, br1, etc...)

37 minutes ago, Siwat2545 said:

This error will occur when the container is set to use host or bridge network, you must use brX (br0, br1, etc...)

I tried setting it to br0 which does get the docker running, but I could not access the web ui - making sure to set a static IP available on my network first!

 

Disregard!  I can access it now. 

Edited December 28, 20214 yr by MrDecepticon

2 minutes ago, MrDecepticon said:

I tried setting it to br0 which does get the docker running, but I could not access the web ui - making sure to set a static IP available on my network first!

can you try port 443(https://) /80 (http://) /3000?, try all of them.

Edited December 28, 20214 yr by Siwat2545

Hi @Siwat2545, I'm having a difficult time finding a solution to get onlyoffice to work.  I followed spaceinvaderone's video and have gone through many posts and suggestions but none gave a full solution. I'm really lost as to what I may be doing wrong,  Can you help shed some light?

 

My latest status:

I can access onlyoffice uring local url using port 4430

If I have: "listen 4430 ssl;" (In the onlyoffixe.subdomain.conf) and try the subdomain URL, I get  "Welcome to you SWAG instance"

If I have: "listen 443 ssl;" (In the onlyoffixe.subdomain.conf) and try the subdomain URL, I get  "400 Bad Request"

 

Attached are some screenshots and diagnostics.

 

Can you please look over and help me to know what I may be doing wrong?

 

Thanks!

tower-diagnostics-20211231-1557.zip

On 12/31/2021 at 4:33 PM, TekDRu said:

Hi @Siwat2545, I'm having a difficult time finding a solution to get onlyoffice to work.  I followed spaceinvaderone's video and have gone through many posts and suggestions but none gave a full solution. I'm really lost as to what I may be doing wrong,  Can you help shed some light?

 

My latest status:

I can access onlyoffice uring local url using port 4430

If I have: "listen 4430 ssl;" (In the onlyoffixe.subdomain.conf) and try the subdomain URL, I get  "Welcome to you SWAG instance"

If I have: "listen 443 ssl;" (In the onlyoffixe.subdomain.conf) and try the subdomain URL, I get  "400 Bad Request"

 

Attached are some screenshots and diagnostics.

 

Can you please look over and help me to know what I may be doing wrong?

 

Thanks!

tower-diagnostics-20211231-1557.zip 125.83 kB · 0 downloads

 

More than likely your .conf file is wrong.  if you are using Swag there is an updated conf file a page or so earlier that worked great for me.  I still don't have this fully sorted out yet, but that should get your reverse proxy working properly.

On 2/28/2021 at 4:25 AM, showstopper said:

# only office doc server


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

    server_name external_dns_subdomain.*;

    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_app OnlyOfficeDocumentServer;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_max_temp_file_size 2048m;
    }
}

 

 

Thanks @dbs179!   This worked for me!

 

Really appreciate it.

Anyone running Homebridge, any issues with it?

YES!

OK!
If anyone is having problems with the spaceinvader guide getting the 400 error
***proxy_set_header Host $host;***
^^^
This right here is the problem!
Comment that out, and it'll work, I don't know why, I don't know what it does, but that's the problem!

You'll also need to comment out
proxy_redirect off;

Because it gives that line 19 error, not sure what that's about either, but the logs point straight to it so I can see people have worked it out.

But
#                proxy_set_header Host $host;

That's the poison causing the 400 error.

******For bonus points, those wanting to secure their onlyoffice, you need to add the following to the onlyoffice docker*****

Variable
Name:secret
Key:JWT_ENABLED
Value:true

and

Variable
Name:Secret Key
Key:JWT_SECRET
Value: password123

Then you can add password123 in your secret key right under ONLYOFFICE docs address for a secure connection

*mic drop*
That took me like 5 hours, enjoy it!

PS: Change "password123" to something else, that's my password and no one else is allowed to use it, I own the NFT
 

Anyone know the default adguard password? I am stuck in the login screen. 

Have you already had it installed previously?  I just installed it and as part of it's setup its asking me for a user name and password

I got onlyoffice document server working with NC but is there a way to disable the welcome page? More specifically the test example button? I don't have the test running so the button gives 502 error, but I would just feel better if that button didn't show up at all.

On 11/20/2021 at 4:39 AM, ZachunRAID said:

What do I need to add to my config file to display logs?

 

"Cannot show logs. "log" option is not configured correctly in your Homebridge config.json file."

I’m having this issue also. Any solution?

 

On 10/4/2021 at 6:20 AM, ab5g said:

Hi Siwat2545 - I am on Unraid 6.10-RC1 and I get the following error when the container starts. 

It is easily fixed by chmod 640 etc/ssl/private/ssl-cert-snakeoil.key

 

Can you incorporate this into the container image please ?

 

 

2021-10-04 04:10:50.135 UTC [135] FATAL: private key file "/etc/ssl/private/ssl-cert-snakeoil.key" has group or world access 
2021-10-04 04:10:50.135 UTC [135] DETAIL: File must have permissions u=rw (0600) or less if owned by the database user, or permissions u=rw,g=r (0640) or less if owned by root. 
2021-10-04 04:10:50.143 UTC [135] LOG: database system is shut down pg_ctl: could not start server Examine the log output. ...fail! * Starting RabbitMQ Messaging Server rabbitmq-server ...done. Waiting for connection to the localhost host on port 5432 
Waiting for connection to the localhost host on port 5432 
Waiting for connection to the localhost host on port 5432 
Waiting for connection to the localhost host on port 5432 
Waiting for connection to the localhost host on port 5432 
Waiting for connection to the localhost host on port 5432 

 

Has your server crashed with RC1? if so, try to delete the container and image and reinstall it.

On 12/9/2021 at 2:34 PM, sonic6 said:

Hey @ab5g did you found a solution?

Nope. Living with it

i cant seem to get the 

h265ize docker to run

i installed the defaults  and when i run it  it wont start i checked the log  it tells me this

 

chmod: cannot access '/mnt/user/h265ize/output/init.sh': No such file or directory

 

am i supposed to do something other then install the docker?

Re h265ize

 

First, thanks for making this docker image.  It should be very useful, but hasn't been working for me.

 

The input directory is monitored and the file queue loaded, and the script is loaded into the temp directory just fine.  The log files say that the files are processed, but gives an error that "ffmpeg exited with code 1".   There is an output version with size 0b made in the temp folder.  I tried reinstalling ffmpeg within the container, but found that ffmpeg version is already the latest version.

 

Second, I really support the comment above about passing options through during the build of the docker image.  For example, the bit depth of 8 is default, but the h265ize page says that this can be changed with the variable --bitdepth (https://github.com/FallingSnow/h265ize)

 

thanks for your advice!

 

[log]

[h265ize]: Processing ABCD-1080p Remux.mkv...

[h265ize]: [verbose] Encoding started at Wed, 12:02 PM
[h265ize]: [verbose] Getting metadata...
[h265ize]: [verbose] Resolving video streams...
[h265ize]: [verbose] Upconverting...
[h265ize]: [verbose] Setting video bit depth...
[h265ize]: [verbose] Mapping streams...
[h265ize]: English
[h265ize]: Spanish; Castilian
[h265ize]: [verbose] Detecting auto crop...
[h265ize]: Crop Detection: 1/12
[1000D[1A[2K[h265ize]: Crop Detection: 2/12
[1000D[1A[2K[h265ize]: Crop Detection: 3/12
[1000D[1A[2K[h265ize]: Crop Detection: 4/12
[1000D[1A[2K[h265ize]: Crop Detection: 5/12
[1000D[1A[2K[h265ize]: Crop Detection: 6/12
[1000D[1A[2K[h265ize]: Crop Detection: 7/12
[1000D[1A[2K[h265ize]: Crop Detection: 8/12
[1000D[1A[2K[h265ize]: Crop Detection: 9/12
[1000D[1A[2K[h265ize]: Crop Detection: 10/12
[1000D[1A[2K[h265ize]: Crop Detection: 11/12
[1000D[1A[2K[h265ize]: Crop Detection: 12/12
[h265ize]: [alert] Output will be cropped to 1920x1072. Originally 1920x1080
[h265ize]: [verbose] Mapping HE Audio streams...
[h265ize]: [verbose] Setting ffmpeg settings...
[h265ize]: [verbose] Encoding video...
[h265ize]: ffmpeg exited with code 1:
[h265ize]: [verbose] Finished encoding at Wed, 12:03 PM (a minute)

Pardon my idiocracy...

 

Using AdGuard container - When turning on encryption it has a spot for "Set certificate file path." Is there a way to write certs with SWAG container and point AdGuard to where SWAG stores certs so that they're automatically always up to date? I just don't know what the URL structure would be to go from AdGuard container back to SWAG where certs are kept. 

 

Any advice?

22 hours ago, blaine07 said:

Pardon my idiocracy...

 

Using AdGuard container - When turning on encryption it has a spot for "Set certificate file path." Is there a way to write certs with SWAG container and point AdGuard to where SWAG stores certs so that they're automatically always up to date? I just don't know what the URL structure would be to go from AdGuard container back to SWAG where certs are kept. 

 

Any advice?

I don't use SWAG but I'm pretty sure that you can bind the swag's cert directory to something like /cert in the adguard container and access it from there