- CollEc-run - example.com

Certificate
by Christian Zimmermann 06 Sep '24

06 Sep '24

The CollEc certificate expired on 2024-08-10 Christian Zimmermann https://ideas.repec.org/zimm/

4 10

Certificate
by Christian Zimmermann 27 Aug '24

27 Aug '24

CollEc seems to have an invalid or expired certificate, browsers refuse the address. Christian Zimmermann https://ideas.repec.org/zimm/

2 1

Let's Encrypt certificate expiration notice for domain "collec.repec.org"
by Thomas Krichel 23 Jul '24

23 Jul '24

Can we cancel this certificate, now we use the wildcard? ----- Forwarded message from Let's Encrypt Expiry Bot <expiry(a)letsencrypt.org> ----- Hello, Your certificate (or certificates) for the names listed below will expire in 6 days (on 2024-07-30). Please make sure to renew your certificate before then, or visitors to your web site will encounter errors. We recommend renewing certificates automatically when they have a third of their total lifetime left. For Let's Encrypt's current 90-day certificates, that means renewing 30 days before expiration. See https://letsencrypt.org/docs/integration-guide/ for details. collec.repec.org For details about when we send these emails, please visit: https://letsencrypt.org/docs/expiration-emails/ In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. For any questions or support, please visit: https://community.letsencrypt.org/ Unfortunately, we can't provide support by email. To learn more about the latest technical and organizational updates from Let's Encrypt, sign up for our newsletter: https://letsencrypt.org/opt-in/ If you are receiving this email in error, unsubscribe at: http://delivery.letsencrypt.org/track/unsub.php?u=30850198&id=406fc8fb735f4… Please note that this would also unsubscribe you from other Let's Encrypt service notices, including expiration reminders for any other certificates. Regards, The Let's Encrypt Team ----- End forwarded message ----- -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21599th day.

1 0

Let's Encrypt certificate expiration notice for domain "collec.repec.org"
by Thomas Krichel 10 Jul '24

10 Jul '24

This has just appeared my desk. I suggest you we the *.repec.org wildcard certs instead. They are here root@siche ~ # ls /etc/letsencrypt/opt/live/repec.org/ cert.pem chain.pem fullchain.pem privkey.pem README Their home is on iripa, but they are mirrored all other servers. ----- Forwarded message from Let's Encrypt Expiry Bot <expiry(a)letsencrypt.org> ----- From: Let's Encrypt Expiry Bot <expiry(a)letsencrypt.org> To: krichel(a)openlib.org Subject: Let's Encrypt certificate expiration notice for domain "collec.repec.org" Hello, Your certificate (or certificates) for the names listed below will expire in 19 days (on 2024-07-30). Please make sure to renew your certificate before then, or visitors to your web site will encounter errors. ... ----- End forwarded message ----- -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21586th day.

3 4

Cron <root@helos> docker ps --filter "ancestor=collec_app" --filter "status=running" | grep "days ago" | awk '{print $1}' | xargs --no-run-if-empty docker stop | xargs --no-run-if-empty docker rm]
by Thomas Krichel 09 Jul '24

09 Jul '24

We have a crontab that sends me this output. There are 100 lines of gibberish. Can we silence this? ----- Forwarded message from Cron Daemon <root(a)openlib.org> ----- From: Cron Daemon <root(a)openlib.org> To: root(a)openlib.org Subject: Cron <root@helos> docker ps --filter "ancestor=collec_app" --filter "status=running" | grep "days ago" | awk '{print $1}' | xargs --no-run-if-empty docker stop | xargs --no-run-if-empty docker rm 2d3adc16df93 b22a4c7f71d0 991cc7bf0819 [lines deleted] ----- End forwarded message ----- -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21585th day.

2 1

Launching forever
by Christian Zimmermann 16 Jun '24

16 Jun '24

I am not getting the CollEc site to finish loading. Christian Zimmermann https://ideas.repec.org/zimm/

3 3

New middleware version
by Düben, Christian 08 May '24

08 May '24

A new version of the middleware has been released today. May I update the software on Helos? Christian Düben Doctoral Candidate Chair of Macroeconomics Hamburg University Germany christian.dueben(a)uni-hamburg.de<mailto:christian.dueben@uni-hamburg.de> https://www.christian-dueben.com

2 3

CollEc online
by Düben, Christian 11 Apr '24

11 Apr '24

CollEc is online again. Docker upgrades keep taking it offline. Christian Düben Doctoral Candidate Chair of Macroeconomics Hamburg University Germany christian.dueben(a)uni-hamburg.de<mailto:christian.dueben@uni-hamburg.de> https://www.christian-dueben.com

2 3

back to the old?
by Thomas Krichel 12 Mar '24

12 Mar '24

Hi, https://collec.repec.org yields https://collec.repec.org/app/collec_app it looks like this is dead, since there has been no fix. Should I revive the old version of the site? -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21462nd day.

2 4

Re: [CollEc] CollEc app not starting
by Thomas Krichel 01 Feb '24

01 Feb '24

Düben, Christian writes > The middleware appears to not be compatible with those upgrades. I > guess that an upcoming upgrade will fix it. Until then, CollEc is not > available. I think we can ill afford to be out for that long. we are talking about docker-compose-plugin:amd64 (2.21.0-1~ubuntu.22.04~jammy, 2.24.1-1~ubuntu.22.04~jammy) docker-ce-cli:amd64 (5:24.0.7-1~ubuntu.22.04~jammy, 5:25.0.0-1~ubuntu.22.04~jammy), docker-ce:amd64 (5:24.0.7-1~ubuntu.22.04~jammy, 5:25.0.0-1~ubuntu.22.04~jammy) docker-ce-rootless-extras:amd64 (5:24.0.7-1~ubuntu.22.04~jammy, 5:25.0.0-1~ubuntu.22.04~jammy) I am trying to find these packages on ubuntu but no luck. Even for dockers-ce https://packages.ubuntu.com/search?suite=default&section=all&arch=any&keywo… I warned about Ubuntu. What we could do is reinstall the entire server as Debian, and then we should be able to get historic versions through Debian snapshot. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21418th day.

2 11