I’ve only just installed Nextcloud on my Synology docker server and every few mins I get an error saying it’s unable to find a file… But not sure where this error is coming from:
GuzzleHttp\Exception\ClientException: Client error: `GET https://nas.bh.com:444/apps/richdocumentscode/proxy.php?req=/hosting/capabilities`
resulted in a `404 Not Found` response:
<html> <head><title>404 Not Found</title></head> <body> <center><h1>404 Not Found</h1></center> <hr><center>nginx</c (truncated...)
What could be causing this?
I have changed the external docker port to 444 as the reverse proxy is using 443.
/config/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Middleware.php - line 69:
GuzzleHttp\Exception\RequestException::create("*** sensiti ... *")
/config/www/nextcloud/3rdparty/guzzlehttp/promises/src/Promise.php - line 204:
GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensiti ... *")
/config/www/nextcloud/3rdparty/guzzlehttp/promises/src/Promise.php - line 153:
GuzzleHttp\Promise\Promise::callHandler()
/config/www/nextcloud/3rdparty/guzzlehttp/promises/src/TaskQueue.php - line 48:
GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}("*** sensiti ... *")
/config/www/nextcloud/3rdparty/guzzlehttp/promises/src/Promise.php - line 248:
GuzzleHttp\Promise\TaskQueue->run()
/config/www/nextcloud/3rdparty/guzzlehttp/promises/src/Promise.php - line 224:
GuzzleHttp\Promise\Promise->invokeWaitFn()
/config/www/nextcloud/3rdparty/guzzlehttp/promises/src/Promise.php - line 269:
GuzzleHttp\Promise\Promise->waitIfPending()
/config/www/nextcloud/3rdparty/guzzlehttp/promises/src/Promise.php - line 226:
GuzzleHttp\Promise\Promise->invokeWaitList()
/config/www/nextcloud/3rdparty/guzzlehttp/promises/src/Promise.php - line 62:
GuzzleHttp\Promise\Promise->waitIfPending()
/config/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php - line 187:
GuzzleHttp\Promise\Promise->wait()
/config/www/nextcloud/lib/private/Http/Client/Client.php - line 226:
GuzzleHttp\Client->request()
/config/www/nextcloud/apps/richdocuments/lib/Service/CapabilitiesService.php - line 135:
OC\Http\Client\Client->get()
/config/www/nextcloud/apps/richdocuments/lib/Service/CapabilitiesService.php - line 73:
OCA\Richdocuments\Service\CapabilitiesService->refetch()
/config/www/nextcloud/apps/richdocuments/lib/AppInfo/Application.php - line 80:
OCA\Richdocuments\Service\CapabilitiesService->getCapabilities()
/config/www/nextcloud/lib/private/AppFramework/Bootstrap/FunctionInjector.php - line 66:
OCA\Richdocuments\AppInfo\Application->OCA\Richdocuments\AppInfo\{closure}("*** sensiti ... *")
/config/www/nextcloud/lib/private/AppFramework/Bootstrap/BootContext.php - line 50:
OC\AppFramework\Bootstrap\FunctionInjector->injectFn()
/config/www/nextcloud/apps/richdocuments/lib/AppInfo/Application.php - line 135:
OC\AppFramework\Bootstrap\BootContext->injectFn()
/config/www/nextcloud/lib/private/AppFramework/Bootstrap/Coordinator.php - line 200:
OCA\Richdocuments\AppInfo\Application->boot()
/config/www/nextcloud/lib/private/legacy/OC_App.php - line 213:
OC\AppFramework\Bootstrap\Coordinator->bootApp()
/config/www/nextcloud/lib/private/legacy/OC_App.php - line 141:
OC_App::loadApp()
/config/www/nextcloud/lib/base.php - line 1031:
OC_App::loadApps()
/config/www/nextcloud/index.php - line 36:
OC::handleRequest()
share your docker compose or docker run. Also provide FULL container logs, they begin with our ascii logo. You should probably also mention what reverse proxy you use and whether you can reach nextcloud without the error when you bypass whatever the proxy is. We do not support or recommend deploying containers with the synology ui as it breaks things.
I think you missed the comment We do not support or recommend deploying containers with the synology ui as it breaks things.
I suggest you create these with docker compose or docker run (compose is obviously going to be much better and simpler)
You also didn’t answer what reverse proxy you’re using , we support our reverse proxy SWAG.
Your new logs don’t show any errors, since you said those logs are when NOT using the reverse proxy, I can only conclude the issue is your reverse proxy or the fact that you used the broken syno ui to deploy the containers.
The reverse proxy is running on a different machine… only reference was to the port it was using 444 instead of 443 but it is Nginx Proxy Manager, not running on Synology therefore not even related to the issue. The reason I bought it up, was because it showed 444 in the next cloud logs.
I thought possibly that the port number could be causing issues in next cloud?
The port was changed due to a conflicting port on the NAT routing rules into my network from the internet.
I will try figuring out how to use docker compose, never done that before because I was only ever shown how to use the syno UI.
if you need to change the port, you could just do 444:443 which is probably the same as what you have. You didn’t show your bind mounts, so you’d need to adjust those in the above snippet. That just goes in a file called something like docker-compose.yml then you type docker-compose up -d and that’s pretty much it. much simpler than the UI and no surprises.
If you need some help, you’re welcome to join our discord and ask in #other-support which is where we give best-effort help for things we don’t officially support.
NPM ^
You blanked out what you accessed the system by, it should be an rfc1918 ip address which should not need to be blanked out. https://<docker host ip>:444
that said, i can clearly see letters in what you blanked out i want you to ONLY use IP
