Publishing to DO with docker problem

After creating a new DO server:
-SSH connects ok
-webserver ok
-database ok

Created Project targets, both local and remote showing no errors.
Test connection in targets results in ‘Connection successful’

After publishing to the production, remote target no errors shown.
But checking for content using the domain name: prismsoftware.solutions just get the site cant be reached error message or page not found depending on 1 of 2 possible scenarios.

There are 2 Issues

  1. I noticed this:

why is the status message trying to locate /reception when the url specifies /index.???
It appears that the browser is trying to open another projects url, that i previously opened and closed.

  1. Even when the browser is not displaying the conflict as shown in issue 1
    when viewing, the url prismsoftware.solutions, on another machine I still get the ‘This site cant be reached.‘ error message.

I have also tried creating a new project from scratch, everything appears to connect ok. Publishing to the remote droplet does not raise any error, but again I cannot view ant content on any browser on any machine.

It appears that the ‘docker deploy name‘ in the remote target ‘production‘ has swapped with the other project I opened. I cannot change to the correct name because the select does not show it as an option…

What is going on???

Hi James,

I’m not sure about the url redirection or docker deploy name in the production remote target. However, there have been some compatibility problems between Wappler (running Traefik) and Docker v29.x.x on the Linux instances. So, I’ll start by checking if that’s the cause of the connection errors.

  1. Log on the remote DO instance
  2. Type Docker --version in the terminal
  3. If Docker version is v29.x.x, then Docker will need to be downgraded to v28.x.x - follow the instructions provided by Ben in this post:
    ✅ Ubuntu 24.04 now pushing Docker 29.1.3 in general release cycle - #8 by bpj