Docker endpoint for "default" not found when trying to deploy to remote server

Wappler General Bugs
#1

Wappler Version: 5.5.2
Operating System: Windows
Server Model: Node
Database Type: Postgres
Hosting Type: Docker / DigitalOcean

Expected behavior

When clicking Deploy to push to my remote server it should successfully deploy

Actual behavior

When clicking Deploy to push to my remote server I’m getting a new error docker endpoint for "default" not found.

If I test the connection to the remote server in Project settings, then I get this error

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.10.0)
  compose: Docker Compose (Docker Inc., v2.15.1)
  dev: Docker Dev Environments (Docker Inc., v0.0.5)
  extension: Manages Docker extensions (Docker Inc., v0.2.17)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.23.0)

Server:ERROR: error during connect: Get "http://xxx.243.169.83:2375/v1.24/info": dial tcp xxx.243.169.83:2375: connectex: No connection could be made because the target machine actively refused it.
errors pretty printing info
Error Occurred Testing Docker Connection!

How to reproduce

I’m not sure how to replicate it. Here’s a video of the issue.

2023: The Year in Review
#2

@Teodor, any ideas?

I’m not sure why port 2375 is being refused. Is this something on the Docker container?

I do not have any ports blocked currently. I am able to access the remote server via 443/80 for the regular part of the app and Wappler had no issues originally deploying the app, and a few deploys after the initial deploy. I’m not sure if this is an issue caused by upgrading Wappler or because I’m allowing Beta features.

#3

Bumping for support.

#4

Did you upgrade docker desktop recently?

#5

Not that I’m aware of. If it did, it would have been an auto-update. I started to look through .wappler files to try to understand where it’s trying to connect to port 2375, but I haven’t seen it so far. Everything I’ve seen is specifying port 80 <> 3000.

I did find a reference to port 2375 and Docker on github, but not sure what to do with the knowledge.

1 Like
#6

Still using the same version, but there is an update available.

image
image1117×473 44.5 KB

1 Like
#7

Run this:

docker context ls

#8

image

#9

It seems your meta file might have corrupted itself.

Check this:

And this:

There are several workarounds posted. Make sure you backup files you touch.

Error deploying with Docker
#10

This one also:

#11

Yeah, looks like the issue is fixed in 4.17. Going to update. :slight_smile:

1 Like
#12

@JonL here’s what it returns.

image
image1306×82 11 KB

#13

Well slap me silly and call me Steven. That appears to have fixed my ability to deploy/publish to the remote server, but testing the Target connection still has the same error.

image

#14

At least you can deploy.

The error on the testing looks like a connectivity issue if it’s not related to some weird caching happening since the error you already fixed updating.

Is the firewall correctly configured?

#15

I haven’t setup a firewall yet. All ports are open.

#16

Is it a new server? Or was all this working before and now it doesn’t?

Ubuntu (if that is what you are using) comes with its own firewall.

ufw allow 2375/tcp
ufw reload
#17

It was working before. As far as I’m aware, I didn’t change anything within Wappler that would affect this and I definitely didn’t change anything on the cloud server.