Thanks Florian! These hiccups make up for a great learning experience. On Thu, Jul 16, 2020, 3:42 AM Florian <[email protected]> wrote:
> Yeah sure, I can try to write up some things. > > I did notice that uploads don't work as in: I see upload progress, no > errors, but also no files when the upload ends. > Once I iron out those quirks I'll attempt to clean up the notes I made as > I went. > > Also tgulacsi78, thank you for sharing your configs. They do differ > somewhat from what I have, so they might come in handy! > > On Wednesday, 15 July 2020 at 19:52:01 UTC+2 [email protected] wrote: > >> Can you please share a blog post on how you achieved this setup >> consisting of ec2 + s3 + caddy? >> I'm sure this would be helpful to many! >> Thanks! >> >> On Wed, Jul 15, 2020, 10:25 PM Gulácsi Tamás <[email protected]> wrote: >> >>> Great! I use it behind caddy, without tls, too. >>> ------------------------------ >>> *From:* [email protected] <[email protected]> on behalf of >>> Florian <[email protected]> >>> *Sent:* Wednesday, July 15, 2020 4:54:47 PM >>> *To:* Perkeep <[email protected]> >>> *Subject:* Re: TLS handshake error: upgrade your ACME client >>> >>> Found it .. the "without tls" did not get through to me apparently! >>> Running Perkeep without https did solve this issue. >>> >>> On Wednesday, 15 July 2020 at 16:35:49 UTC+2 Florian wrote: >>> >>> Okay, I've been able to set that up and use the keyc/cert from Caddy for >>> the Perkeep server. >>> >>> For some reason it now keeps asking me for basic auth, even if I have >>> that set to `auth: "none"`, and I don't have basic auth set up on Caddy. >>> So basicly I'm stuck on that prompt dialog. >>> >>> If you happen to have a working instance of this, would you mind sharing >>> your Caddyfile? >>> >>> >>> On Wednesday, 15 July 2020 06:43:57 UTC+2, tgulacsi78 wrote: >>> >>> It does need upgrading. For a workaround, put it behind caddy ( >>> caddyserver.com), without tls. >>> >>> >>> >>> On Wed, Jul 15, 2020 at 12:29 AM +0200, "Florian" <[email protected]> >>> wrote: >>> >>> Hi, >>> >>> I've just started using Perkeep, setting it up on an Amazon EC2 with an >>> attached S3 bucket and I have been able to hook it up to one of my domain >>> names. >>> However, I have been trying to get HTTPS to work, but keep getting the >>> following printed: >>> >>> "403 urn:acme:error:unauthorized: Account creation on ACMEv1 is >>> disabled. Please upgrade your ACME client to a version that supports ACMEv2 >>> / RFC 8555. See >>> https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 >>> for details." >>> >>> Since I'm mostly a front-end dev, this is all a little on the far side >>> of my knowledge and comfort zone, so I was hoping someone could point me in >>> the right direction. >>> >>> Fwiw, my config looks like this: >>> >>> { >>> "auth": "userpass:<user>:<secret>:+localhost", >>> "https": true, >>> "baseURL": "https://<mydomain>", >>> "listen": ":443", >>> "camliNetIP": "", >>> "identity": "<identity>", >>> "identitySecretRing": >>> "/home/ec2-user/.config/perkeep/identity-secring.gpg", >>> "s3": "<s3 config>", >>> "packRelated": true, >>> "levelDB": "/home/ec2-user/var/perkeep/index.leveldb" >>> } >>> >>> Thanks in advance to anyone taking the time, >>> Regards, >>> >>> Florian >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Perkeep" group. >>> >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> >>> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/perkeep/637fca78-ff01-4b01-a7cd-3fa7ba930a49o%40googlegroups.com >>> <https://groups.google.com/d/msgid/perkeep/637fca78-ff01-4b01-a7cd-3fa7ba930a49o%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Perkeep" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/perkeep/af336f42-d18f-48bb-9b41-41d5d44cbad5n%40googlegroups.com >>> <https://groups.google.com/d/msgid/perkeep/af336f42-d18f-48bb-9b41-41d5d44cbad5n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Perkeep" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/perkeep/VI1P192MB028520BD81D6422FE808229FF27E0%40VI1P192MB0285.EURP192.PROD.OUTLOOK.COM >>> <https://groups.google.com/d/msgid/perkeep/VI1P192MB028520BD81D6422FE808229FF27E0%40VI1P192MB0285.EURP192.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer> >>> . >>> >> -- > You received this message because you are subscribed to the Google Groups > "Perkeep" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/perkeep/2440b298-e32b-427e-86d4-215dae61835dn%40googlegroups.com > <https://groups.google.com/d/msgid/perkeep/2440b298-e32b-427e-86d4-215dae61835dn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/perkeep/CANWB9SqOnbub8045OazwzNM13Ubb0hWzUv0Qb%2BuFgmHDqeE2EQ%40mail.gmail.com.
