Hi,
I have Wappler 5.0.4 brand new installation on brand new computer (macOS with M1).
creation with old procedure is smooth while creating new servers with Resource Manager I always got the following message:
Error in server access setup: ssh: connect to host 67.205.138.46 port 22: Connection refused
Server setup failed!
The server is done successfully by wappler but then I get this message
Here the screenshot:
Any Idea how to solve the problem ?
thank you
Roberto
See:
Also in your case seems something might be blocking port 22 and tge ssh access.
So check if not any firewalls are in the way.
You can also run “system check” from the context menu of the server in Resource Manager
Hello George,
thank you for your reply.
I made some test, sometimes working, sometimes not. Here all the steps:
I made a brand new SSH KEY
Then I added it to SSH Agent
From resource Manager I create a new server
Resource Manager has the red dot in the server. But if I do “Refresh”, he get the IP and seems working
In the Resouce manager the Server is with the red point
I do not understand what I m doing wrong… any suggestion?
thank you
Roberto
Roberto,
When creating a new server you really have to wait till the process is fully completed. The server will boot and software will update and during that time ssh is not yet available naturally as it is being installed.
So wait till the final server created successfully prompt and all spinners gone and then you can access it.
George,
I did nothing. I just waited. Got this red error message and nothing…
EDIT: I checked again: after this error:
nothing happen
Hmm what kind of server and provider you choose?
Digital Ocean
1 CPU with 25 GB SSD 1 GB ram 1Tb transfer (6 USD)
Image: UBUNTU 2.04 LTS x64
Try adding the SSH key to the SSH agent from the context menu and then choose to execute a system check on the server from its context menu.
Running System Check …
Check Docker installation on Server …
Updating System Packages …
Retry (1) Updating System Packages …
System Updated:
Hit:1 http://mirrors.digitalocean.com/ubuntu jammy InRelease
Hit:2 http://mirrors.digitalocean.com/ubuntu jammy-updates InRelease
Hit:3 http://mirrors.digitalocean.com/ubuntu jammy-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Reading package lists…
Setup Docker on server …
Retry (1) Updating System Packages …
Retry (2) Updating System Packages …
System Updated:
Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:2 https://repos.insights.digitalocean.com/apt/do-agent main InRelease
Hit:3 http://mirrors.digitalocean.com/ubuntu jammy InRelease
Hit:4 http://mirrors.digitalocean.com/ubuntu jammy-updates InRelease
Hit:5 http://mirrors.digitalocean.com/ubuntu jammy-backports InRelease
Reading package lists…
W: https://repos.insights.digitalocean.com/apt/do-agent/dists/main/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Setup Docker on server …
Docker Installed:
Reading package lists…
Building dependency tree…
Reading state information…
The following additional packages will be installed:
bridge-utils containerd dns-root-data dnsmasq-base pigz runc ubuntu-fan
Suggested packages:
ifupdown aufs-tools cgroupfs-mount | cgroup-lite debootstrap docker-doc
rinse zfs-fuse | zfsutils
The following NEW packages will be installed:
bridge-utils containerd dns-root-data dnsmasq-base docker.io pigz runc
ubuntu-fan
0 upgraded, 8 newly installed, 0 to remove and 41 not upgraded.
Need to get 65.6 MB of archives.
After this operation, 283 MB of additional disk space will be used.
Get:1 http://mirrors.digitalocean.com/ubuntu jammy/universe amd64 pigz amd64 2.6-1 [63.6 kB]
Get:2 http://mirrors.digitalocean.com/ubuntu jammy/main amd64 bridge-utils amd64 1.7-1ubuntu3 [34.4 kB]
Get:3 http://mirrors.digitalocean.com/ubuntu jammy/main amd64 runc amd64 1.1.0-0ubuntu1 [4087 kB]
Get:4 http://mirrors.digitalocean.com/ubuntu jammy/main amd64 containerd amd64 1.5.9-0ubuntu3 [27.0 MB]
Get:5 http://mirrors.digitalocean.com/ubuntu jammy/main amd64 dns-root-data all 2021011101 [5256 B]
Get:6 http://mirrors.digitalocean.com/ubuntu jammy-updates/main amd64 dnsmasq-base amd64 2.86-1.1ubuntu0.1 [354 kB]
Get:7 http://mirrors.digitalocean.com/ubuntu jammy/universe amd64 docker.io amd64 20.10.12-0ubuntu4 [34.0 MB]
Get:8 http://mirrors.digitalocean.com/ubuntu jammy/universe amd64 ubuntu-fan all 0.12.16 [35.2 kB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 65.6 MB in 1s (54.6 MB/s)
Selecting previously unselected package pigz.
(Reading database … 64234 files and directories currently installed.)
Preparing to unpack …/0-pigz_2.6-1_amd64.deb …
Unpacking pigz (2.6-1) …
Selecting previously unselected package bridge-utils.
Preparing to unpack …/1-bridge-utils_1.7-1ubuntu3_amd64.deb …
Unpacking bridge-utils (1.7-1ubuntu3) …
Selecting previously unselected package runc.
Preparing to unpack …/2-runc_1.1.0-0ubuntu1_amd64.deb …
Unpacking runc (1.1.0-0ubuntu1) …
Selecting previously unselected package containerd.
Preparing to unpack …/3-containerd_1.5.9-0ubuntu3_amd64.deb …
Unpacking containerd (1.5.9-0ubuntu3) …
Selecting previously unselected package dns-root-data.
Preparing to unpack …/4-dns-root-data_2021011101_all.deb …
Unpacking dns-root-data (2021011101) …
Selecting previously unselected package dnsmasq-base.
Preparing to unpack …/5-dnsmasq-base_2.86-1.1ubuntu0.1_amd64.deb …
Unpacking dnsmasq-base (2.86-1.1ubuntu0.1) …
Selecting previously unselected package docker.io.
Preparing to unpack …/6-docker.io_20.10.12-0ubuntu4_amd64.deb …
Unpacking docker.io (20.10.12-0ubuntu4) …
Selecting previously unselected package ubuntu-fan.
Preparing to unpack …/7-ubuntu-fan_0.12.16_all.deb …
Unpacking ubuntu-fan (0.12.16) …
Setting up dnsmasq-base (2.86-1.1ubuntu0.1) …
Setting up runc (1.1.0-0ubuntu1) …
Setting up dns-root-data (2021011101) …
Setting up bridge-utils (1.7-1ubuntu3) …
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Setting up pigz (2.6-1) …
Setting up containerd (1.5.9-0ubuntu3) …
Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.service.
Setting up ubuntu-fan (0.12.16) …
Created symlink /etc/systemd/system/multi-user.target.wants/ubuntu-fan.service → /lib/systemd/system/ubuntu-fan.service.
Setting up docker.io (20.10.12-0ubuntu4) …
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Adding group `docker’ (GID 120) …
Done.
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
Processing triggers for dbus (1.12.20-2ubuntu4) …
Processing triggers for man-db (2.10.2-1) …
Running kernel seems to be up-to-date.
Services to be restarted:
systemctl restart packagekit.service
Service restarts being deferred:
systemctl restart unattended-upgrades.service
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
Server was setup successfully!
But after that the server is still:
And watching better, now one key disappeared by the SSH Key manager.
What if I delete the Keys in the Docker/ machine folder and I re install Wappler from zero?
How can I delete the old keys from the SSH Agent ?
Sorry I don’t really understand what you mean.
In general you just need one personal SSH key that you reuse for all your servers and providers. You don’t have to create a different key each time.
Ok I had two or three keys I added to try the resource manager.
Will reset and will reinstall Wappler from scratch
I was able to recreate the issue with the initial SSH Access denied error.
Seems Digital Ocean is not very quick in creating servers sometime, so we will be increasing our wait time for more bulletproof experience. So will improve that in the next update.
Anyway even if that fail after doing system check (after. minute or so), it should go all fin and you should be able to deploy after the system is ready.
Ok thank you very much George and thank you for your support on Sunday too!!
Fixed in Wappler 5.1
This topic was automatically closed after 47 hours. New replies are no longer allowed.
