DigitalOcean docker production target with cloud database bug?

JBM · May 22, 2024, 4:21pm

Do I need to change the setup from cloud providers - ssh to socket?????

George · May 22, 2024, 4:24pm

No, it is al SSH now

But you haven’t answered my question above, how did you created your server ( not database)

Apple · May 22, 2024, 4:25pm

Please don't, wait for George's reply

Cheese · May 22, 2024, 4:26pm

Our build is a legacy Project prior to Resource Managers complete integration. I'd wait for George to respond before doing anything @JBM

JBM · May 22, 2024, 4:31pm

everything via resource manager, I imported it as I created another test project and created it there...hope that makes sense

George · May 22, 2024, 5:22pm

Well if you can connect to the server it should be fine. Try to open an SSH Terminal from the context menu of the server.

This should trust the host and the question to trust it shouldn’t come any longer on deploy.

JBM · May 22, 2024, 5:41pm

Ok George opened ssh terminal

and then got this:

Error: All configured authentication methods failed at doNextAuth (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\client.js:865:21) at tryNextAuth (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\client.js:1082:7) at tryNextAgentKey (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\client.js:1091:11) at USERAUTH_FAILURE (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\client.js:423:20) at 51 (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\protocol\handlers.misc.js:408:16) at Protocol.onPayload (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\protocol\Protocol.js:2059:10) at AESGCMDecipherNative.decrypt (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\protocol\crypto.js:987:26) at Protocol.parsePacket [as _parse] (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\protocol\Protocol.js:2028:25) at Protocol.parse (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\protocol\Protocol.js:313:16) at Socket.<anonymous> (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\client.js:775:21) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Socket.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
Error: Timed out while waiting for handshake at C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\ssh2\lib\client.js:1116:23 at sentryWrapped (C:\Users\jim\AppData\Local\Wappler\resources\app\node_modules\@sentry\browser\cjs\helpers.js:92:17)

JBM · May 23, 2024, 10:01am

Hi George, still getting problems

got this when I opened ssh connection -
Please type 'yes', 'no' or the fingerprint: yes
Warning: Permanently added '167.99.83.90' (ED25519
) to the list of known hosts.
root@167.99.83.90: Permission denied (publickey).
root@prism-app:~#

George · May 23, 2024, 10:16am

and what are the problems now?

JBM · May 23, 2024, 10:44am

got this when I opened ssh connection -
Please type 'yes', 'no' or the fingerprint: yes
Warning: Permanently added '167.99.83.90' (ED25519
) to the list of known hosts.
root@167.99.83.90: Permission denied (publickey).
root@prism-app:~#

And after trying to deploy the production connection get the same error message as mentioned on numerous occasions above:


[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)  docker:default
[+] Building 0.0s (0/0)                                                                                                                docker:default 
time="2024-05-23T11:47:44+01:00" level=warning msg="C:\\Users\\jim\\OneDrive\\Documents\\imported_kasa_app\\web_app\\.wappler\\targets\\production\\docker-compose.yml: `version` is obsolete"

So fundamentally the same problems that have not been resolved from the start of this post...

JBM · May 23, 2024, 11:34am

As we don't seem to be any closer for me to connect to a DO production do server with a managed database without getting an error stating that the docker-compose.yml version is obsolete could you advise me as what would be the quickest way to a solution?

delete the DO droplet and reinstate from the wappler resource manager with option of deleting the DO managed databases and reinstate from the wappler resource manager.
create 2 seperate droplets, one for development and one for production simplifying the connection process.
uninstall the latest version of docker and reinstall an earlier version.

OR
Pursue further options as suggested in this post.

looking forward to advice...

Cheese · May 23, 2024, 11:58am

You can ignore this error or like I said above simply delete the first line of the file. By the looks of it you need to generate a new SHH key but I do not know how to do this using the Resource Manager?

Can you build and deploy to Docker locally without issue?

Cheese · May 23, 2024, 12:07pm

Can you browse to:

.docker/machine/machines/PROJECT_NAME

This is a hidden (you may need to enable show hidden files if not already enabled) directory located on the root level of your OS. This directory should contain your SSH keys for the Project.

You should see similar to the below (I'm on Ubuntu but Windows and Mac look similar).

JBM · May 23, 2024, 12:08pm

Hi Cheese,
Simply removing the first line of the file makes no difference, still hangs with same error message oddly.

Yes docker works with the local web server and remote develop cloud db, but just constantly refuses to work the remote development web server.

Cheese · May 23, 2024, 12:11pm

That is strange, almost suggests you have two of the same instance? Removing the line and building should no longer show the version error... However it is not a failure point and is just a warning so don't worry too much.

Cheese · May 23, 2024, 12:18pm

We have two Targets. A local Target for Development and a Remote Target for Production, both connect to a Digital Ocean Database Cluster. We did not use Resource Manager as they were created before it was fully integrated but there is no reason you can't go this route and set the Targets up manually in the Project Settings (using Sockets rather than SSH and the Resource Manager). Maybe try this..? Leave your current Project as it stands and simply start a new one to see if everything works, you won't get charged for it as you can simply delete it on DO, or keep it and move across to it once it is working (that is up to you).

JBM · May 23, 2024, 12:22pm

Great thanks Cheese for your help, will create another project as you suggested and see what I can come up with.

Cheese · May 23, 2024, 12:23pm

Stick with it James you will get there and then wonder why it all seemed so difficult to begin with. Just teething issues. We all have them. I'll be about most of the day so will keep an eye on updates to this thread.

JBM · May 23, 2024, 1:26pm

Hi Cheese again, thanks for your words of encouragement been working this problem for almost a week now....really frustrating

Opened up a new project created a new droplet via the resource manager added the targets, tried sockets but I just cannot add portainer for ssl or deploy anything on the DO server producing the same error 'version obsolete'.

The problem is the 'version obsolete' error message brings up a question in the command line which I can never answer so it hangs forever

George · May 23, 2024, 1:26pm

Well it seems to me that your SSH key is not valid for the server. You are getting access denied.

That would explain also the docker deploy problems.

Did you use the same SSH key that the server was created with?

Also were you able to successfully open an SSH Terminal from the context menu of the server?

And is the key added to the SSH Agent in the Resource Manager?