@charaoh On Cloudron each app runs in a container. So apps cannot access the host (ssh) and vice versa. You can instead upload the files and access the files using the Web Terminal - https://docs.cloudron.io/apps/#web-terminal . This "terminal" is run in the context of the app container.

Which app are you referring to or are you referring to the system wide SMB server? For the latter, this is not supported by Cloudron. Installing and configuring other services on the same server where Cloudron is installed, will eventually break either Cloudron or those services. Maybe you can briefly explain the use-case you have on hand?

There is an allow list file, but you have to access it from ssh. It should be in the docs.

@jodumont said in Docker Swarm or MultiHost Support?: It is possible to have 2 cloudrons under the same domain.tld ? The main domain needs to be different, in order for the dashboard to have a unique URL for each Cloudron (the my.domain.com). It could however be a subdomain for one of the machines. And you could afterwards add the main domain to the second machine, in order to install apps on it too. For example, you could have Machine 1 with main domain domain.com, management dashboard on my.domain.com, and apps on app1.domain.com, app2.domain.com Machine 2 with main domain machine2.domain.com, management dashboard on my.machine2.domain.com, and apps on app3.domain.com, app4.domain.com

@mastadamus Can you add that as a feature request and mention this thread?

@nebulon no worries.. I found it by searching the admin page

Hey, Thanks for the quick response (and to Johannes for the support ticket solving too). That is a fine workaround for me until there's a cancel button implemented some day. At least I can do some tests now, thanks guys great job.

@girish I found this when i clicked update: [image: 1639218382101-61f3d999-30ce-405d-9639-1e1c26465759-image.png] Both my apps are running and are accessible. I now tried stopping the Nextcloud instance and started it. And it the app the 1 dead app is now 2 alive and 0 dead. Now i could update normally. Not sure what i missed in the first place but now works. Thanks for the help

@d19dotca @Lonkle , had the same issues with Cloudron installation on vpsdime. Fixed it using the same workarounds in this thread. Seems to work fine now. Not sure if there will be any issues in the future..

@jdaviescoates thanks!

@girish Seemed like maybe Ubuntu was finishing some updates on boot which was blocking ssh from starting. I was pinging on 80 and 443 ports but ssh wasn't responding on 22 or 202 for a while.

@blackshot7 are you able to run those commands manually and check if they succeed ? maybe some DNS resolution is not working?

We detect the IP using curl https://api.cloudron.io/api/v1/helper/public_ip . Can you check what this returns and why this doesn't return your public IP? You can also use something like https://whatismyipaddress.com/ which should return the same value.

@xaddison the prune is done automatically when needed in the code. Most likely the containers that got removed are the ones that were "stopped". Cloudron runs cron jobs of apps in containers, for example. They will be in stopped state after finishing a run but will be reused in the next run. As for images, not sure what it cleaned up. Do you have the output of what it removed?

@girish Thank you!

@d19dotca What a read!

Followed this guide and everything is back to normal. Thanks guys! https://docs.cloudron.io/guides/import-postgresql/

@girish said in Docker Container - Unable To Install Cloudron: @brutalbirdie said in Docker Container - Unable To Install Cloudron: Maybe adding Docker in there as well to prevent confusion. Done! The fast guy!

The upgrade guides should mostly be identical for upgrading Ubuntu. The Cloudron guide has maybe couple of additional notes/configuration for making sure things are running after upgrade. What error are you hitting when upgrading following either of the docs? I suspect they hit the same error.