[Bug]: Seafile service shows Network error when trying to upload files

[clho40]

Error Message and Logs

The Seafile image does not seem to be working. I was able to run the application and was able to sign in, but get the following error when trying to upload a file.

I have tried to add additional environment variables as stated here https://forum.seafile.com/t/network-error-on-fresh-server/23143/3 but there was no effect.

@nktnet1 do you have any idea?

Steps to Reproduce

1. On Coolify, deploy a Seafile service. Change the Seafile URL to https://yourdomain.com
2. Login to the Seafile at https://yourdomain.com
3. Go to any Library and upload a file

Example Repository URL

No response

Coolify Version

v4.0.0-beta.434

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

No response

[nktnet1]

@clho40 Do you see anything in the logs?

Please provide the client-side logs (press F12 or inspect the page, go to the Console tab, then perform the action again. You may also want to see the Networks tab to investigate the request).

Please also provide the server-side logs - you can do this by opening a terminal session in your seafile docker container and viewing the files listed here:

• https://manual.seafile.com/11.0/maintain/logs/

e.g. by going to /shared/seafile/logs/

Also, if you've updated your domain at some point after the point of initialisation, make sure you've updated your seahub config accordingly.

[clho40]

Aha, good catch. I do see the following error from the browser console:

commons.97a1bd68.js:2   POST https://http//seafile-80-a8ow0o8og88o4s4wsgks8kg4.xxx.xxx.xxx.xxx.sslip.io/seafhttp/upload-aj/4ea1aeb1-6c93-4dce-b8eb-8dcf19b41ce7?ret-json=1 net::ERR_NAME_NOT_RESOLVED

There is only one environment variable that holds this value:
SERVICE_URL_SEAFILE_80=http://seafile-80-a8ow0o8og88o4s4wsgks8kg4.xxx.xxx.xxx.xxx.sslip.io

And it is unchangeable. Any idea how do we sort this?

[nktnet1]

It's unchangeable because it's set based on your configured domain.

You will need to change your domain instead :).

You may need to also update your seahub_setting.py afterwards.

[clho40]

Sorry I did not make it clear, I did change my configured domain, but the value was updated to another environment variable:

SERVICE_URL_SEAFILE=https://mycustomdomain.com

but the SERVICE_URL_SEAFILE_80 has been populated with the coolify self-generated domain, and was not changeable

[nktnet1]

I suggest editing seahub settings for now and redeploy, then see if anything changes.

I'm not too sure about your environment variables - you could also try opening a terminal in the seafile container and use printenv to see if the values are consistent with what you see in the UI.

Finally, feel free to submit a PR for the template if you think there's a mistake in there:

• https://github.com/coollabsio/coolify/blob/v4.x/templates/compose/seafile.yaml

I'm no longer running Seafile on Coolify so I'm not sure if I'll be able to help debug further, but hopefully you'll be able to get it resolved.

[Cinzya]

You probably just need to change the SEAFILE_SERVER_HOSTNAME to use SERVICE_URL_SEAFILE. So basically just remove the 80 from it.

    environment:
      - SERVICE_URL_SEAFILE_80
      - SEAFILE_SERVER_HOSTNAME=${SERVICE_URL_SEAFILE}
...

[ShadowArcanist]

Hello @clho40 !

I have submitted a PR with a Fix: #6973 , I have included some steps on the PR description to deploy this service without having to wait for the PR to be merged so you can deploy the service anytime you want :)