I’ve been having some odd issues with deploying anything via Docker through the Resource Manager after doing a factory reset of my PC. (its been a few years so it was needed)
Doing any sort of Deploy used to take 10-15 seconds to complete now it takes 2 minutes, if it even succeeds.
There is no output until the deployment is complete or it fails where before it showed me each step, such as downloading the docker images.
I cannot deploy the Project at all anymore will error out every time. See below:
When deploying new services, the new service will always start at a default port even though it may already be taken. I need to manually check all deployed services for which ports are used to not use that port then manually increment it. Did not have to do that before.
Checking Project Settings - Test Connection succeeds but again output is not visible until its completed.
Doing system check on the Docker Server succeeds.
Using my Local as the target I see all the output I would normally see, such as the image pulls and building steps. Completes fast as it would normally do.
What I’ve tried so far.
Cleared out all docker containers
Rebuild docker containers
Restarted Docker Server
Update Docker Server
Generate a new SSH Key using the Project Path option and use the generated .pub file as an authorized key to the server. Add that key it generated into the Resource Manager.
Remove Docker Server
Add Docker Server.
If after I deploy a new service then try and use the Open Service Terminal, Wappler will lock up and has to be force closed. I can still open the terminal on the server itself just fine.
Using v6 b15. I don’t believe its an issue with that specific version as I was using it fine before I did the factory reset. Am I missing something on my local PC for all this missing functionality?
Npm pushed a big upgrade recently (last Sunday week) that caused chaos. We couldn’t build for 16 hours. It’s worth upgrading your npm and node to 16 at a minimum as a result
I have the previous SSH key and tried deploying new SSH keys. Both connect just fine inside of Wappler and I can connect outside of Wappler just fine as well using those keys.
Here is another error I received, from Wappler. Hard to see but its Error: Timed out while waiting for handshake.
The live servers are also made with Resource Manager right? And are you able to connect with an SSH terminal to them? There is an option for this in the context menu of each server: “Open SSH Terminal”
Doing so will check if your SSH keys work for the servers.
Also make sure the SSH Agent is running, it is also listed in the Resource Manager and you can also start it from its context menu if it is not running.
Yes that part does work, using the Open SSH Terminal and opens quickly.
The SSH agent is running. It first was not running when I first opened Wappler after the factory reset and Wappler was unable to start it, errored out. I started it manually via windows services and wappler sees it fine after that.
I’ve removed the databases in attempts to troubleshoot so makes sense I am getting the half green circle right now but here is the screenshot after clicking on a staging target on a custom docker cloud server. Again what normally takes 10-15 seconds to deploy had to wait 3-4 minutes for it to error out.
Works just fine on Docker Desktop on the local Windows PC, its deploying to the docker cloud server where I am having the issues. Going to test on another computer and will see if it works any different. Will also look at your link. May be tomorrow before I can follow up.
Found an older download I had of Docker Desktop and uninstalled the latest I downloaded which was 4.25. Installed 4.21.1 and now everything is back to normal. So the problem is one of the versions in-between it seems.
I believe I am all back to normal so far. I did see that WSL2 was already set for Docker and verified it was using that by checking the version in powershell however I ran wsl --install via powershell and then after a reboot we seem to be all back to normal now. Seems just installing docker on its own does not install all the required components.
Had an odd issue where Wappler removed my custom server then when trying to add it back it was asking for a ssh key inside of the Wappler project folder which was never generated by me using format I did not use. I generated a new key to get around the issue and now it works again.
