I created a new remote server (Vultr) and imported it as an existing custom server in the Resources Manager.
The SSH key that has been used to create this server is project based and is available under the SSH Agent. I can open the SSH terminal from the server context menu and I have checked, there's an entry for the SSH key in the known hosts file.
When I run System Check command on the imported server, the Running System Check message appears and after 2-3 minutes, the process fails. These are the error messages that appear in the Wappler console.
Error in server access setup:
status: done
Server setup failed!
Is it a bug or have I missed a step during the setup?
I have restarted Wappler a few times with logging and Debug Mode enabled, reproduced the error, but there's no log file available at this location ~/Library/Application Support/Wappler/.
Has the location of log file changed in the latest MacOS Sonama?
Was there a update to this problem? I just started and it's on the OS you were using?
do you know if version 25, works or do I have to drop back to 22.03 that is the only other one they offer
I haven't had any issues with Ubuntu 24.04 running on the Linux box lately. Any incomptability issues might have been fixed in one of the many Ubuntu and Docker updates since last year. I haven't yet upgraded any remote server to Ubuntu v25.
I am encountering this issue again when running System Check command in the Resources Manager.
I have setup a new remote server running ubuntu v25.04 (initially had ubuntu v24.04.02 LTS installed on the server and that also didn't work) and added it as a custom server in the Resources Manager. The server is accessible via ssh root@x.x.x.x correctly.
However, when I run System Check to install Docker and its dependencies on the server, the process fails and shows this error message:
Running System Check ...
Error in server access setup: status: error
Server setup failed!
A System Check on all the existing servers running 24.04.02 LTS is completing without any issues.
So, it seems to be an issue with a brand new remote server setup. Any help in troubleshooting this issue is greatly appreciated.
I upgraded ubuntu from v24.04.02 LTS to 25.04 by running do-release-upgrade commands. v24.04.02 can be upgraded to v25.04 by first upgrading to v24.10. Both upgrades were undertaken only after the new releases were available.
I have experienced this issue before with v24.04. And I'm getting the same error on a new server regardless of ubuntu v24.04.02 LTS or v25.04
I see from the logs that cloud-init, the server setup that automatically runs on new server creation, has failed. This is a provider specific setup done by the provider.
You could puzzle what is wrong in there, or just create a brand new server that goes without problems.
If you wish to puzzle, you can connect with SSH terminal to the server and check it.
A cloud-init status error with exit code 1 indicates a critical failure and suggests a serious problem with the system or potentially a bug in cloud-init itself. This means cloud-init was unable to recover from the error, and the system likely needs further investigation.
Troubleshooting Steps:
Check Logs:
Examine /var/log/cloud-init.log and /var/log/cloud-init-output.log for details on the failure.
Verify Dependencies:
Ensure that all services and packages required by cloud-init are running and installed correctly.
Run with Debugging:
Try running cloud-init init --local or cloud-init init --local --debug to see the output.
Review Configuration:
Check the contents of /etc/cloud/cloud.cfg and /etc/cloud/user-data for any syntax errors or misconfigurations.
Check for Network Issues:
If network configuration is involved, verify that network services are running and that cloud-init can access the necessary resources (like IMDS for Azure).
Consider Hardware Issues:
If the error persists after checking software, hardware issues, such as a faulty drive or memory, should be investigated.
Report the Bug:
If you suspect a bug in cloud-init, report it to the cloud-init issue tracker.