ECONNREFUSED 127.0.1.1:80

Yes, i am running on HTTP instead of HTTPS. It’s fully local here in my lab and i am the only user. :wink:

Backend running.
Whenever i want to access a whiteboard file i get FetchError: http://mynextcloudurl/index.php/apps/whiteboard/number failed, reason ECONNREFUSED 127.0.1.1:80

Native install on Ubuntu 22.04, UFW disabled.
Whiteboard 1.0.5
Admin tells me all is okeydokey. Whiteboard backend server is configured and connected.

Should i add 127.0.1.1 to the list of authorised domains, maybe? Ignore the message?

Container log:

ton@nextcloud:~/whiteboard$ sudo docker-compose up
Starting whiteboard_nextcloud-whiteboard-server_1 ... done
Attaching to whiteboard_nextcloud-whiteboard-server_1
nextcloud-whiteboard-server_1  | 
nextcloud-whiteboard-server_1  | > whiteboard@1.0.5 server:start
nextcloud-whiteboard-server_1  | > node websocket_server/main.js
nextcloud-whiteboard-server_1  | 
nextcloud-whiteboard-server_1  | Using default in-memory adapter
nextcloud-whiteboard-server_1  | Listening on port: 3002
nextcloud-whiteboard-server_1  | Server started successfully on port 3002
nextcloud-whiteboard-server_1  | Using existing JWT_SECRET_KEY from environment
nextcloud-whiteboard-server_1  | cachedTokenStorage StorageManager {
nextcloud-whiteboard-server_1  |   strategy: GeneralLRUStrategy {
nextcloud-whiteboard-server_1  |     cache: LRUCache {
nextcloud-whiteboard-server_1  |       ttl: 600000,
nextcloud-whiteboard-server_1  |       ttlResolution: 1,
nextcloud-whiteboard-server_1  |       ttlAutopurge: true,
nextcloud-whiteboard-server_1  |       updateAgeOnGet: false,
nextcloud-whiteboard-server_1  |       updateAgeOnHas: false,
nextcloud-whiteboard-server_1  |       allowStale: false,
nextcloud-whiteboard-server_1  |       noDisposeOnSet: false,
nextcloud-whiteboard-server_1  |       noUpdateTTL: false,
nextcloud-whiteboard-server_1  |       maxEntrySize: 0,
nextcloud-whiteboard-server_1  |       sizeCalculation: undefined,
nextcloud-whiteboard-server_1  |       noDeleteOnFetchRejection: false,
nextcloud-whiteboard-server_1  |       noDeleteOnStaleGet: false,
nextcloud-whiteboard-server_1  |       allowStaleOnFetchAbort: false,
nextcloud-whiteboard-server_1  |       allowStaleOnFetchRejection: false,
nextcloud-whiteboard-server_1  |       ignoreFetchAbort: false,
nextcloud-whiteboard-server_1  |       getRemainingTTL: [Function (anonymous)],
nextcloud-whiteboard-server_1  |       [Symbol(Symbol.toStringTag)]: 'LRUCache'
nextcloud-whiteboard-server_1  |     }
nextcloud-whiteboard-server_1  |   }
nextcloud-whiteboard-server_1  | }
nextcloud-whiteboard-server_1  | Using existing JWT_SECRET_KEY from environment
nextcloud-whiteboard-server_1  | [57] Ton Machielsen has joined 57
nextcloud-whiteboard-server_1  | [57] Starting sync: { hasInputData: false, hasToken: true }
nextcloud-whiteboard-server_1  | [57] Determining data to update: { hasInputData: false, hasCurrentData: false, hasToken: true }
nextcloud-whiteboard-server_1  | [57] Fetching server data: {}
nextcloud-whiteboard-server_1  | FetchError: request to http://nextcloud/index.php/apps/whiteboard/57 failed, reason: connect ECONNREFUSED 127.0.1.1:80
nextcloud-whiteboard-server_1  |     at ClientRequest.<anonymous> (file:///app/node_modules/node-fetch/src/index.js:108:11)
nextcloud-whiteboard-server_1  |     at ClientRequest.emit (node:events:507:28)
nextcloud-whiteboard-server_1  |     at emitErrorEvent (node:_http_client:104:11)
nextcloud-whiteboard-server_1  |     at Socket.socketErrorListener (node:_http_client:518:5)
nextcloud-whiteboard-server_1  |     at Socket.emit (node:events:507:28)
nextcloud-whiteboard-server_1  |     at emitErrorNT (node:internal/streams/destroy:170:8)
nextcloud-whiteboard-server_1  |     at emitErrorCloseNT (node:internal/streams/destroy:129:3)
nextcloud-whiteboard-server_1  |     at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
nextcloud-whiteboard-server_1  |   type: 'system',
nextcloud-whiteboard-server_1  |   errno: 'ECONNREFUSED',
nextcloud-whiteboard-server_1  |   code: 'ECONNREFUSED',
nextcloud-whiteboard-server_1  |   erroredSysCall: 'connect'
nextcloud-whiteboard-server_1  | }
nextcloud-whiteboard-server_1  | [57] Server data is invalid, recovering from backup: {}
nextcloud-whiteboard-server_1  | [57] Recovered from backup: {}
nextcloud-whiteboard-server_1  | [57] Room updated: { elementsCount: 0, filesCount: 0 }
nextcloud-whiteboard-server_1  | [57] Backup created: { elementsCount: 0, filesCount: 0 }

nextcloud-whiteboard-server_1 | FetchError: request to http://nextcloud/index.php/apps/whiteboard/57 failed, reason: connect ECONNREFUSED 127.0.1.1:80

Since Whiteboard is running in a container, 127.0.1.1 is the container itself. I assume that’s what your nextcloud hostname resolves to? That won’t work from inside the container.

nextcloud resolves to the server where Nextcloud is natively running. The Whiteboard server docker container is running on the same host as where nextcloud is running natively (not in a container).

Whiteboard is running in a container, correct?

If so, from the container’s perspective, things like localhost / 127.0.0.1 resolve to itself. They are independent from the underlying host.

I get that. That’s why my NEXTCLOUD_URL is set to http://nextcloud and my Whiteboard URL to http://nextcloud:3002