digidoc on Nostr: Potentially VERY stupid question about nostrcheck-server. I've been fighting with ...
Potentially VERY stupid question about nostrcheck-server.
I've been fighting with getting HTTPS fully working for days. Simple Nginx reverse proxy with Certbot. It works on the interface, but not the APIs. Log shows the following on media post attempts:
WARN - RES -> 400 Bad request - Auth header event endpoint is not valid https://mydomain.com/api/v2/media <> http://mydomain.com/api/v2/media
Best I can tell (after turning on debug logging everywhere) Nginx is passing along what it's supposed to ("proxy_set_header X-Forwarded-Proto $scheme;" has been set) but nostrcheck-server just...isn't doing anything with it?... So it works on HTTP, but upon adding SSL this happens, and I haven't been able to find any instructions on how to either make the nostrcheck-server APIs use HTTPS or ignore the difference between the auth header endpoint URLs. I suppose I could go into NIP98.ts and replace "${req.protocol}" with "https", but I'm assuming NIP98 calls for requiring those URLs to be identical for a reason, so that seems like a bad idea...
#asknostr #nostrcheckserver quentin (npub138s…x624)
I've been fighting with getting HTTPS fully working for days. Simple Nginx reverse proxy with Certbot. It works on the interface, but not the APIs. Log shows the following on media post attempts:
WARN - RES -> 400 Bad request - Auth header event endpoint is not valid https://mydomain.com/api/v2/media <> http://mydomain.com/api/v2/media
Best I can tell (after turning on debug logging everywhere) Nginx is passing along what it's supposed to ("proxy_set_header X-Forwarded-Proto $scheme;" has been set) but nostrcheck-server just...isn't doing anything with it?... So it works on HTTP, but upon adding SSL this happens, and I haven't been able to find any instructions on how to either make the nostrcheck-server APIs use HTTPS or ignore the difference between the auth header endpoint URLs. I suppose I could go into NIP98.ts and replace "${req.protocol}" with "https", but I'm assuming NIP98 calls for requiring those URLs to be identical for a reason, so that seems like a bad idea...
#asknostr #nostrcheckserver quentin (npub138s…x624)