Cloudron Forum

@nebulon FINALLY! the mail arrived. So, Discourse was not correctly configured, as for the POP3 host and password. Good to know, I'll document that internally.

Thanks a lot, I really appreciate the time and thouroughness!

When changing POP3 polling host from my.soletic.cloud to mail (the name on the local network?), I get :

If I try mail.soletic.cloud (public address just in case?), I get:

@nebulon This will move the whole cloudron instance's mail server to this name. Aren't there any references I should worry about when doing this? (we're hosting a bunch of services, I don't know all of them)

@nebulon
Yes:

What do you exactly mean by "with mail as the host in discourse" ? My Discourse settings are as above. Host is the default one (my) :

@nebulon I get exactly that (except for the IP address ofc).

@nebulon

CLOUDRON_MAIL_POP3_PORT=9595
CLOUDRON_MAIL_POP3S_PORT=9995
CLOUDRON_MAIL_SMTP_SERVER=mail
CLOUDRON_MAIL_IMAP_SERVER=mail

So that was why the pop3 polling port was 9595 on Discourse. I reverted it to 9595 and tried again replying by email. Still nothing, and the timeout on 9595 is back (at least it's consistent).
Could there be a port conflict? How could I check that?

Bumping this thread in case someone got an idea.

@james Ah yes sure.
POP3 polling enabled and :

Note: POP3 polling port was actually 9595 (and wasn't considered modified by discourse (no green dot)), so that explains the 9595 call (but why was there a 995 call too then?). I just changed it to 995 and tried again to send an email (and waited for the 5 min of polling period), but no luck.

@james As soon as I understand what you mean by that

@james I didn't realize it was necessary, thanks.
I set it up on the 10th of march at 17:49. From this moment, the Discourse logs hasn't shown any TCP timeout on 995 anymore. But mails remain ineffective.
These errors remain afterwards:

I suspect the SMTPServerBusy reveals a new problem?

@james I don't know but it was a bad example, I've got this error for 995 as well:

Reply by email does not work on my Discourse.
Discourse logs say multiple instances of:

Job exception: Timeout to open TCP connection to my.soletic.cloud:9595
Job exception: Timeout to open TCP connection to my.soletic.cloud:995

My mailbox looks good to me:

(I actually just changed the owner to the app, before that it was a user group, not sure if that matters)

And my Discourse mailbox settings as well:

When test-sending an email reply to a Discourse message notification, it seems to be received:

But the message does not reach the Discourse thread to which it replies.

Any help appreciated.

Thanks you guys! Not sure if there's a "solved" button that I'm missing in here but problem and questions solved.

I saw on previous posts that I simply need to delete the plugin folder in /app/code/plugins.

1. Could this be added to the docs please?
2. I would like to backup the plugins directory before proceeding. For this I'm trying to mv plugins plugins.backup but even with gosu cloudron:cloudron before, it fails as parent folder is read-only.
   What is the standard way to proceed?
3. Cloudron is not a Discourse-supported way of self-hosting so docs is scarce. Is there an app.yml somewhere (couldn't find one with find) that lists the plugins or has this been removed?

(I'm on Discourse 2.8.14 if that matters)

Referenced Topic: https://forum.cloudron.io/post/55243
Agreed, how to uninstall plugins should be added to the docs. I can't find the app.yml file in my app.

Would it be possible to have an automation of the upgrades until there are no more upgrades, then? For example a button "upgrade to latest" that would upgrade from 1.0 to 1.1, then without intervention from 1.1 to 1.2, etc.?

I support this.

To clarify, this is a UX bug and not a feature request, because this leads an operator to see "No new updates available" when clicking "Check for updates", while there are new updates, which is misleading.

@nebulon No luck. I always created links with a schema, and IN built-in links parameters (such as $view_url) don't work either. Plus, if you open the unclickable PDF with a PDF editor, no link is detected at all.

@jdaviescoates Yes these were on-the-fly translations. And it seems that you couldn't reproduce my problem. Thanks for checking.

Why yes, I have been asked for a PDF with a clickable link so I provided . Now for an unclickable link (which does sound more appropriate indeed) (same expiration date).