Replies: 2 comments
-
Hey @Supasong , If everything works but Windows Client, isn't it obvious this is a Windows Client bug instead? You should report this issue (with the Zoraxy log or network trace file, if any) to them. |
Beta Was this translation helpful? Give feedback.
-
As far as i had researched, the the windows client does complete different things: it is more or less a Webdav / Webcal Client for files and folders integration to the nextcloud server. for this functionallity the nextcloud windows client (and probably every other webdav/caldav usage) )does require adjustements / specific configuration with headers etc. For nginx, traeffic etc. there are many instructions availible, but zoraxy seems to be "too new", so nothing found so far. i do not know, how to adapt and where to set those kind of modifications. i think runnig nextcloud behind a reverse proxy is a very common usage, so i hope someone else can give me an advice ;) |
Beta Was this translation helpful? Give feedback.
-
Hello,
i am new to homelab services and reverse proxies. my setup is very common:
Debian 12.8 - Docker CE - Portainer
Zoraxy as reverse Proxy
Some services are already successfully running, including dyndns domain setup and LetsEncrypt certificates.
The latest project is my own nextcloud, the installation is running, certificates für https and local split dns are configured.
The only post install steps after creating the Nextcloud CTs had been the zoraxy proxy rule and adding docker host IP to nextcloud config file ("thrusted domains" in /nextcloud/config/config.php )
Whats working:
https://nextcloud.mydmain.dyndns.rg from internel + external -> no errors
Andoid App connect ->no errors
Windows Client .exe -> always get "403 forbidden"
When starting the Windows Client, you have inital only the field for the server adress (i.e. "https:/nextcloud.mydomain.dyndns.org" ). Using this URL in browser, webseite appears and you can login. Using the same URL in Windows Client: 403 error.
i have googled a lot and also asked chatGPT & his frriends, but all information about nextcloud & reverse proxies are related to nginx, traefficm caddy and so on, and I am not able to adapt those things in zoraxy.
i would be glad for help to solve this.
reagards,
supa
Beta Was this translation helpful? Give feedback.
All reactions