Receiving error from recently deployed remote target (getaddrinfo EAI_AGAIN db)

[kfawcett]

I recently setup a remote server and database using the Wappler Resouce Manager and added them in a new Target for my project. During the process the Direct Database Connection was not populated, so I entered the connection details manually.

I can view the remote db tables and create records within the Database Manager, so I know the connection and DB are functioning.

But when I attempt to interact with the remote server via my mobile app I receive the getaddrinfo EAI_AGAIN db error.

{status: "500", code: "EAI_AGAIN", message: "getaddrinfo EAI_AGAIN db",…}
code: "EAI_AGAIN"
message: "getaddrinfo EAI_AGAIN db"
stack: "Error: getaddrinfo EAI_AGAIN db\n    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)"
status: "500"

[kfawcett]

Strangely, the Global Database Connection in Server Actions has the local development server db values. Should these be automatically updated to the remote db server values I set for the new target?

[kfawcett]

Updating the values in the Global Database Connection db was the fix.

[George]

Maybe this is similar problem as:

Io socket.io not working when used with Redis and Traefik

After long investigation with Adriano, I’m happy to say we found the problem. It was Redis configuration when used with Traefik. It was not joining the same network as the rest of the services when Traefik is used. So when Traefik is used the Redis service also need: networks: proxy: ~ so it becomes in the docker-compose.yml redis: image: 'redis:alpine' hostname: 'redis' networks: proxy: ~ volumes: - 'redis-volume:/data' we will fix that in the next u…

and will be solved in the next update

[Teodor]

Fixed in Wappler 5.5.2