Posts made by girish

@homesteadsaga said in Mailtrain RSS Campaign + Wordpress:

my server's ip address seems to be blocked, presumably because some previous DO user was spamming?

Yes, you have to then setup an Email relay in the Email view of Cloudron. The apps will automatically start using the relay to send email without any extra configuration.

when I try to use my site's wordpress feed, I get an error:

Is this inside mailtrain? Where does that screenshot come from?

I noticed there is a mail plugin for wordpress already - do I even need mailtrain in that case? I was not able to get it to work because of (1) above though

You probably do not. Note that mailtrain is only required to send and manage newsletters (for example, to put unsubscribe links in your email etc). If you just want to send email, the wordpress app should work without requiring any configuration. I suspect it cannot send mail because of the problem in 1.

All certs are Let's Encrypt. The SSL issue appears to be something else but I am not 100% sure. Can you tell us a bit more high level of what you are trying to do and we can help out.

@darcyc Yes, correct. In Cloudron, we use the LDAP authentication in BookStack. When LDAP mode is enabled in BookStack, you cannot login as admin anymore. See https://www.bookstackapp.com/docs/admin/ldap-auth/

You may find that you cannot log in with your initial Admin account after changing the AUTH_METHOD to ldap.
To get around this set the AUTH_METHOD to standard, login with your admin account then change it back to
ldap. You get then edit your profile and add your LDAP uid under the ‘External Authentication ID’ field.
You will then be able to login in with that ID.

On Cloudron, the first user will become admin. The roles of rest of the users can be adjusted in BookStack's settings page. I put this info in our docs now - https://cloudron.io/documentation/apps/bookstack/#admin

[1.7.0]

• Fix tags
• Update postinstall
• Add forumUrl

@darcyc Turning off sign ups works for me here. I think the bug is that the "register" link is still shown in the login page despite disabling registration. Bbut if you click register and try to register, one cannot login without an invite code.

[4.2.0]

• Disable registration, if you set or unset explicitly
• Add docs on how to make user an admin

I have pushed an update to Wekan now that disables user registration by default. You can, of course, explicitly turn it on.

@darcyc To make yourself an admin, run this command - https://cloudron.io/documentation/apps/wekan/#admin

@darcyc I am pushing a fix shortly, hold on.

@d19dotca The box code is only the backend code. The frontend code is at https://git.cloudron.io/cloudron/dashboard

I did look into integrating with gogs when I did the GitLab integration. IIRC, the issue was that the gogs APIs for release tracking required a token (unlike GitHub and GitLab). This means that you have to create an account in another gogs/gitea instance (registration is frequently disabled) making it impossible to track. I think we might have to investigate a bit more and report the issue upstream first.

We are holding back updates to 3.23.x because of this bug.

Indeed, currently catch-all has to have the feature to set mailboxes across domains (like aliases).

Ah, I see why. This is because Merge Requests and Forks was disabled. In the past, we had few people submit big PRs and get upset when we it didn't align with what we wanted. It's best to let us know first if you are making big changes. I have enabled it now in any case.

Good question, no clue why it's hidden for the box code alone.

[1.37.4]

• Update GitLab to 13.0.9

[1.3.1]

• Update Mastodon to 3.1.5
• Full changelog
• Security: Fix media attachment enumeration (ThibG)
• Security: Change rate limits for various paths (Gargron)
• Security: Fix other sessions not being logged out on password change (Gargron)

Synapse [1.6.0]

• Update Synapse to 1.16.0
• Full changelog
• Add an option to enable encryption by default for new rooms. (#7639)
• Add support for running multiple media repository workers. See docs/workers.md for instructions. (#7706)
• Media can now be marked as safe from quarantined. (#7718)
• Expand the configuration options for auto-join rooms. (#7763)

[1.24.0]

• Update Tiny Tiny RSS to 68b78ecd3d
• Make php.ini customizable
• Fix tags and screenshots
• Add forum url

@darcyc The first user to login is made the Wekan administrator. There is a Admin Panel under the name and from there you can disable self-registration.

But thanks for bringing this up, this is an important issue. I will fix up the package immediately to disable registration on install by default.

Mmm, have to think how we can expose this feature in a user friendly way. AFAIK, rewrite patterns are specific to the reverse proxy. Currently, we use nginx but this is not exposed to the user. So, we have to settle on some generic url rewrite format and expose this via the UI as well. @mario can you put in some example of what kind of rewrites you would like to see? Or is it just the git clone and the project urls? I imagine rewriting path of commits and files is quite complex.

I also don't know how it might break the app itself (what if the app is using the URLs for something else).

Cloudron won't refresh DNS entries automatically unless some action is performed like app configure etc or the Dynamic DNS feature is enabled. Generally, if you go to network view and put in the local IP, you don't have to worry about those automatic actions as well.