Any news on this?
I would also like to se Plausible in Cloudron app store.
They have gained much traction lately and are GDPR compliant which is nice.
I've tried their service and I liked it so now I am looking for self hosting option.
Plausible on Cloudron would be nice.
@nebulon Super! I can confirm that it is back in the store! Thank you 
@girish No I've not patched manually, I have assumed 
sorry
I assumed the latest update was with the CNAME/A-record fix was live.
The thing was that my home server has been offline for a while and when I started it up it updated to from v7.0.4 to v7.1.3 then v7.1.3 to v7.1.4.
After that the DNS propagation didnt work any longer, as it had done before.
@girish After update I get error when propagating DNS. Or at least I thinks it is related because it worked before.
It is a subdomain pointing to a CNAME (duckdns) and it complains on all nsX.hyp.net.
Apr 09 11:33:38 box:dns/waitfordns resolveIp: Checking if xxx has A record at xxxx
Apr 09 11:33:38 box:dns/waitfordns resolveIp: Checking if xxx has CNAME record at xxxx
Apr 09 11:33:38 box:dns/waitfordns resolveIp: Resolving xxx CNAME record xxx
Apr 09 11:33:38 box:dns/waitfordns isChangeSynced: NS ns1.hyp.net (151.249.124.1) errored when resolve xxx (A): Error: queryA EREFUSED xxx
Apr 09 11:33:38 box:dns/waitfordns waitForDns: xxx at ns ns1.hyp.net: not done
Apr 09 11:33:38 box:dns/waitfordns Attempt 7 failed. Will retry: ETRYAGAIN
Final error message
An error occurred during the install operation: DNS Error: DNS A Record is not synced yet: ETRYAGAIN
Any news on this?
I would also like to se Plausible in Cloudron app store.
They have gained much traction lately and are GDPR compliant which is nice.
I've tried their service and I liked it so now I am looking for self hosting option.
Plausible on Cloudron would be nice.
Not sure this is related but I get WOD on one site and login loading "forever" on another.
Mar 08 11:00:17 (/source/database/database.go:439)
Mar 08 11:00:17 [2021-03-08 10:00:17] pq: null value in column "port" violates not-null constraint
Mar 08 11:00:17 ERRO[0000] pq: null value in column "port" violates not-null constraint device="map[arch:amd64 num_cpu:8]" os="map[name:linux]" runtime="map[go_maxprocs:8 go_numcgocalls:1 go_numroutines:14 name:go version:go1.15.6]" type=notifier
I see this error in two installations on different serveres.
Anyone knows what is wrong?
@caleno said in How to authenticate in gitlab pipline?:
I have token auth activated or at least configured and I can still log inn with Cloudron username and password + 2fa.
I'd like the token auth to work via Gitlab and maybe the case above points to a configuration issue.
I have to investigate further.
BTW. Maybe it is just working for the UI.
I have token auth activated or at least configured and I can still log inn with Cloudron username and password + 2fa.
I'd like the token auth to work via Gitlab and maybe the case above points to a configuration issue.
I have to investigate further.
If I understand it correctly the gitlab integration makes gitlab the authority for docker registry submitting jwt tokens for authentication. To create these tokens you either make a access token deploy token or a personal token (especially if you are using 2fa) and one should be able to authenticate to the registry, correct?
I've tried all sorts of tokens and changing the docker-client in authproxy and nginxconfig without success.
Has anyone manged to get this working? ><
@nebulon Super! I can confirm that it is back in the store! Thank you
Hoi!
I can't find the yourls in the app store anymore, is it removed?
Br,
Lennart