Cloudron Forum

OK, I have bumped this to 512MB for next release.

@nebulon Per https://docs.microsoft.com/en-us/windows/win32/adschema/a-userprincipalname , it's an email address and not a username. Also, see https://ldapwiki.com/wiki/UserPrincipalName which sometimes says email and sometimes username.

@colonelpanic Do you know what your software expects this to be?

@fbartels, you are correct. I read that and used the app to start the Web Clipper service, but I was under the impression that I was starting the Web Clipper on the Joplin server. Instead, it starts up a service on the client or workstation running the Joplin app. I don't think the wording is as "direct" or clear as it could be. Thanks.

@colonelpanic said in Cloudflare Setup Questions:

I assume that renewing the Let's Encrypt certificate would not be an issue with the proxy turned on because Cloudron is using a DNS challenge instead of HTTP challenge. Is that a true statement?

Yes. Proxying can be left turned on, Cloudron will manage to get certs via DNS challenge.

What would be the benefit of creating a Wildcard Origin Cert on Cloudflare and uploading it instead of using Let's Encrypt?

AFAIK, there is no benefit. I think the wildcard origin cert is intended for cases where one cannot get a valid cert via DNS or HTTP automation (like some intranets that block outbound access).

@colonelpanic Looks good !

@girish - that did the trick. I upgraded to 2.3.0-1 and I can log in as before.

@colonelpanic no worries, always good to fix things which come up during real use-cases.

Hi! (Vikunja dev here)

As @girish correctly pointed out, you don't need to enable openid to use the api. In fact, when you're using the Vikunja Frontend or Desktop app it already uses the api. The login endpoint is your way to go to get the api token.

I hope to build "classic" api tokens in the future you may know from other websites (like github) where you can create a long-lived token in the user settings and use it without a login.