[BUG] onlyoffice refuses to connect

gacpac commented 4 days ago

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

when accessing or opening a document i get an error message for connection refused to https://documentserver.mydomain.com.

However if I try manually using the local IP from the onlyofficedocker and also disable certificate verification to force it connect. Trying the same process opening a document it works. It's quite strange unless something has been updated that I must update somewhere

Expected Behavior

The expected behavior should be the current normal operation opening a file and by using https://documentserver.mydomain.com at the settings the file should open without giving me a refused connection.

Steps To Reproduce

Simply try to open a file and make sure the docker for onlyoffice is working and is already going through the reverse proxy

Environment

- OS:Unraid 6.12.10
- How docker service was installed: communityapps, has been running for ages no issues.

CPU architecture

x86-64

Docker creation

docker run
  -d
  --name='OnlyOfficeDocumentServer'
  --net='proxynet'
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="OnlyOfficeDocumentServer"
  -e 'JWT_ENABLED'='true'
  -e 'JWT_SECRET'='jwtsupersecretpassword'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:4430]'
  -l net.unraid.docker.icon='https://github.com/chvb/docker-templates/raw/master/chvb/img/OnlyOfficeDocumentServer.jpg'
  -p '8084:80/tcp'
  -p '4430:443/tcp'
  -v '/mnt/user/appdata/onlyofficeds/logs':'/var/log/onlyoffice':'rw'
  -v '/mnt/user/appdata/onlyofficeds/Data':'/var/www/onlyoffice/Data':'rw'
  -v '/mnt/user/appdata/onlyofficeds/lib':'/var/lib/onlyoffice':'rw'
  -v '/mnt/user/appdata/onlyofficeds/database':'/var/lib/postgresql':'rw'
  -v '/mnt/user/appdata/onlyofficeds/fonts':'/usr/share/fonts/':'rw' 'onlyoffice/documentserver:latest'
d61f410c985ce7d5f7301c658a80be9956ed57da63701750469f1ec7fe39dad5

Container logs

───────────────────────────────────────
Linuxserver.io version: 29.0.3-ls327
Build-date: 2024-06-25T14:59:40+00:00
───────────────────────────────────────

using keys found in /config/keys
Initializing nextcloud 29.0.3.4 (this can take a while) ...
Upgrading nextcloud from 29.0.2.2 ...
Setting permissions
Setting log level to debug
Turned on maintenance mode
Updating database schema
Updated database
Updating <text> ...
Updated <text> to 3.10.1
Starting code integrity check...
Finished code integrity check
Update successful
Turned off maintenance mode
Resetting log level
Initializing finished
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2023-04-13 │ 2024-05-27 │ /config/nginx/nginx.conf                                               │
│ 2024-04-02 │ 2024-06-24 │ /config/nginx/site-confs/default.conf                                  │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.

github-actions[bot] commented 4 days ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

j0nnymoe commented 4 days ago

This isn't a bug, just an issue within your config of your reverse proxy or a networking issue.

Few things to check:

check you can acces it directly from your browser via proxied address
check DNS
make sure you're using split DNS rather than relying on NAT hairpin as I believe that causes nextcloud to trip up.

gacpac commented 4 days ago

I cannot access from the outside via the proxies address if that is what you mean. DNS is good I tried using split dns but it's hard to do when it's the same IP of the unraid server so it hits the wrong address.

On Wed, Jun 26, 2024, 2:12 AM j0nnymoe @.***> wrote:

This isn't a bug, just an issue within your config of your reverse proxy or a networking issue.

Few things to check:

check you can acces it directly from your browser via proxied address

check DNS

make sure you're using split DNS rather than relying on NAT hairpin as I believe that causes nextcloud to trip up.

— Reply to this email directly, view it on GitHub https://github.com/linuxserver/docker-nextcloud/issues/447#issuecomment-2190810865, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALNULE54ZKINKNVD6QBEIQTZJJLWPAVCNFSM6AAAAABJ5C3PPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJQHAYTAOBWGU . You are receiving this because you authored the thread.Message ID: @.***>

linuxserver / docker-nextcloud