Closed argovaerts closed 3 years ago
Can you please show me the exact error you got? There should be more information on the command line or in docker-compose logs
for Ekster.
I haven't tried the auth with a Known instance, so I'm not sure what kind of differences there are with other systems.
So more information about the error would be helpful.
What I already know from the information you send is that Ekster expects a JSON value, but gets something else. It would be useful to know what the something else is.
The only logs relating to auth.go are (from docker-compose logs --tail="10"
):
[36mredis_1 | [0m 1:M 27 Jul 2020 11:33:14.013 * Background saving started by pid 20
[36mredis_1 | [0m 20:C 27 Jul 2020 11:33:14.020 * DB saved on disk
[36mredis_1 | [0m 20:C 27 Jul 2020 11:33:14.022 * RDB: 0 MB of memory used by copy-on-write
[36mredis_1 | [0m 1:M 27 Jul 2020 11:33:14.114 * Background saving terminated with success
[36mredis_1 | [0m 1:M 27 Jul 2020 18:01:33.004 * 1 changes in 3600 seconds. Saving...
[36mredis_1 | [0m 1:M 27 Jul 2020 18:01:33.008 * Background saving started by pid 21
[36mredis_1 | [0m 21:C 27 Jul 2020 18:01:33.013 * DB saved on disk
[36mredis_1 | [0m 21:C 27 Jul 2020 18:01:33.014 * RDB: 0 MB of memory used by copy-on-write
[36mredis_1 | [0m 1:M 27 Jul 2020 18:01:33.108 * Background saving terminated with success
[33mweb_1 | [0m 2020/07/27 17:07:21 hubbackend.go:242: Getting feeds for WebSub
[33mweb_1 | [0m 2020/07/27 17:17:21 hubbackend.go:242: Getting feeds for WebSub
[33mweb_1 | [0m 2020/07/27 17:27:21 hubbackend.go:242: Getting feeds for WebSub
[33mweb_1 | [0m 2020/07/27 17:37:21 hubbackend.go:242: Getting feeds for WebSub
[33mweb_1 | [0m 2020/07/27 17:47:21 hubbackend.go:242: Getting feeds for WebSub
[33mweb_1 | [0m 2020/07/27 17:57:21 hubbackend.go:242: Getting feeds for WebSub
[33mweb_1 | [0m 2020/07/27 18:01:32 auth.go:74: Skipping unsupported rels in Link header: http://webmention.org/ https://q4.re/webmention/
[33mweb_1 | [0m 2020/07/27 18:01:32 auth.go:74: Skipping unsupported rels in Link header: webmention https://q4.re/webmention/
[33mweb_1 | [0m 2020/07/27 18:01:32 auth.go:74: Skipping unsupported rels in Link header: hub https://withknown.superfeedr.com/
[33mweb_1 | [0m 2020/07/27 18:01:32 auth.go:74: Skipping unsupported rels in Link header: self https://q4.re/
I have added some error handling around content types in auth codes / tokens. Perhaps this helps catching this problem.
It's the content-type: ERROR: "unknown content-type \"application/x-www-form-urlencoded\" while verifying authorization_code
.
I wasn't sure that this was the reason. So thanks for the added error handling. I may have some Known plumbing to do.
Looks like this is fixed in idno.