If you have a VPS elsewhere, you can open an ssh tunnel to it pointing a public port on the VPS to the internal cloudron install to get to the interface. That will cause other problems since it's not reachable on port 80/443.

@girish Perhaps take a look at it from the pull perspective vs push. Maybe even originating the refresh from the mail container side, triggering the others.

I am currently debugging that instance, but just for others to read up, using nginx -s reload as root usually reveals the syntax errors in config files right away, like it was in this instance as well.

@kingkobra813 Can you try running the script again and check if you get the same error? Looks like maybe nginx.org was maybe down temporarily? You can also check if this works: wget http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/nginx_1.18.0-2~xenial_amd64.deb

@nebulon Thank you for taking a look! My problem has just been solved! It started for me because your DOCS did not make it clear that Creating a Mailbox was a whole separate Necessity even for the ADMIN. And that as an ADMIN who Added a User with the whole Email Invitation sent, user responding, creating their own Username, and Saving this DID NOT by DEFAULT at least finish the process by Adding a new mailbox corresponding to the new User . I never guessed that THE ADMIN him or herself of the Cloudron installation would not have access AS THE ADMIN to setup Master default parameters for the Email App itself! In your docs after following along with the entire Email setup down to the check the Status instructions at last continuing down the page it merely says, casually, as if an Option -- *Mailbox Add Mailboxes can be created for Users and Groups on a per-domain level. To do so, simply create them in the Email view.* Mailboxes can be created for Users when it should really be highlighted as Now mailboxes must be set up here for your users if you intend to offer this as a feature. Nothing indicating that we are continuing in the Enabling Emails for Users instructions or after all of the above it still won't work. That not even the ADMIN now enacting all these steps Must manually install an Email box for him/herself. How about "Finally, you must Finish this process by adding each User's Mailbox manually. These were not created automatically when you finished creating the User. In fact, You must first make an Email Box for yourself with Superadmin privileges or you will not be able to Login to the Email application to customize it according to your preferences. It was finally only by reading carefully https://forum.cloudron.io/topic/4529/cloudron-email-wrong-usernam that I realized any advice I received about my email problem was ASSUMING that I knew this -- even though everytime I read your Docs I was assuming that the Mailboxes were automatically installed, certainly for the Admin first of all. I'd recommend really emphasizing this in your docs as a clear Step 1 through Step 10(?) process REQUIRED Final step or not even the Cloudron Admin can enter his own Email installation.

@austinsonger Regarding Linode and Mail - default is blocked by Linode: https://www.linode.com/docs/guides/running-a-mail-server/ Sending Email on Linode In an effort to fight spam, Linode restricts outbound connections on ports 25, 465, and 587 on all Linodes for new accounts created after November 5th, 2019. If you have a need to send mail from your Linode, we ask that you first configure (1) valid DNS A records and (2) rDNS records for any Linodes that you plan to use to send mail. Then, open a Support ticket from the Linode Manager – we’ll ask you to provide the name of the Linode(s) that will be used for mailing. Once you’ve completed those steps and provided that information, our Support team will be happy to review your request.

@robin pushed a commit to at least give some explanation for 401 https://git.cloudron.io/cloudron/cloudron-cli/-/commit/d90b23c8b561f29f444145d40e4097cb098e5fa1 Apparently no token or invalid token provided to the REST api currently both returns 401.

@mattplaygamez might be better next time to create a new forum thread for separate issues. From your video, I think what is misunderstood is, that the config files for admins will use the user/usernames from your Cloudron, so if you Cloudron user is called foobar then put that username in the config file for the admin role. Maybe we can make this clearer in the docs.

@girish Wow that worked perfectly, thank you so much!

This problem is not reproducible anymore.

Thanks for the quick response!

@leggias hm getting a SIGSEGV is odd here. If you like you can enable remote SSH support and send us a mail to support@cloudron.io mentioning your dashboard domain. Then we can take a direct look at your setup to get down to the issue.

Thanks very much! I've tested it and now it works ok. Will you be able to run your tests multi language?

@girish I patched my docker.js manually, and I can confirm that port 53 is now exposed on all interfaces, as I would expect! Thanks!

@girish @nebulon I did not follow the upgrade tutorial for 16.04 → 18.04 → 20.04 entirely because I have some minor adjustments on the server that were blocking the upgrade. Also, there was a minor issue with docker in the past, where I edited the file /etc/apt/sources.list.d/docker.list so this whole problem was my fault

@debossnow said in I don't understand Linode install of cloudron: How do I confine different applications to be installed in the directory of the VPS I am choosing to install into? Just to re-iterate. This is not possible with linode marketplace images, it's not designed to work that way. You cannot choose "app x" and say install it in this existing VPS. Each app always installs on a fresh linode.

DMARC is about email security. Traditionally this was about inbound protection, where DMARC can be used. Though, DMARC is more about outbound email protection.

@np_cloudron The Cloudron admin credentials and SSH credentials are different. The CLI credentials would have been set when you installed Ubuntu. Not sure where you got the ISO from, but maybe it has some default login? The enable SSH feature is for Cloudron support team to access your server. You should be able to access your server regardless of that.

@savity you have to reboot the server using your VPS control panel or "reboot" via SSH. Do not use the reboot button in Cloudron dashboard, it doesn't work. We will make a new release most likely end of this month (6.4) where it will get fixed.