Hi, I'm getting this error when trying to follow an account from a gnusocial instance running nightly.
Scenario:
Gnusocial version: 2.0-dev (nightly) - RemoteFollow plugin active
Following remote accounts is posible for some mastodon, pleroma and gnusocial v1.20.x instances.
When confirmation button pressed on following remote account from gnusocial v2.0-dev (nightly) account, next error is received in web-browser: "Internal Server Error. An unknown error occurred."
nginx access and error logs don't show this error
This is the log from web-console (some data is ofuscated or omitted for privacy reasons)
Hi, I'm getting this error when trying to follow an account from a gnusocial instance running nightly.
Scenario:
- Gnusocial version: 2.0-dev (nightly) - RemoteFollow plugin active
- Following remote accounts is posible for some mastodon, pleroma and gnusocial v1.20.x instances.
- When confirmation button pressed on following remote account from gnusocial v2.0-dev (nightly) account, next error is received in web-browser: "Internal Server Error. An unknown error occurred."
- nginx access and error logs don't show this error
This is the log from web-console (some data is ofuscated or omitted for privacy reasons)
````
URL:https://ratoncitos.p4g.club/main/remotefollowsub
Method:POST
Remote address:xxx.xxx.xxx.xxx
Status: 500 Internal server error
POSThttps://ratoncitos.p4g.club/main/remotefollowsub
[HTTP/2.0 500 Internal Server Error 11104ms]
HTTP/2.0 500 Internal Server Error
server: nginx
date: Thu, 29 Aug 2019 16:35:37 GMT
content-type: text/html; charset=utf-8
set-cookie: PHPSESSID=*****************; path=/
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding,Cookie
link: <https://ratoncitos.p4g.club/main/amcd.json>; rel="acct-mgmt"; type="application/json"
Host: ratoncitos.p4g.club
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: es-AR,es;q=0.8,en-US;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate, br
Referer: https://ratoncitos.p4g.club/main/remotefollowsub?profile=https%3A%2F%2Fkhp.ignorelist.com%2Fuser%2F1
Content-Type: application/x-www-form-urlencoded
````
POST /main/remotefollowsub] Handled serverError (500) but cannot output into desired format (NULL): 'Unable to connect to tls://ratoncitos.p4g.club:443. Error: Connection timed out'
POST /main/remotefollowsub] ServerErrorAction: 500 Unable to connect to tls://ratoncitos.p4g.club:443. Error: Connection timed out
In case it is useful, this is what i get when trying to follow you from another v2 node:
<code>POST /main/remotefollowsub] HTTPClient: HTTP POST https://ratoncitos.p4g.club/inbox.json - 400 Bad Request
POST /main/remotefollowsub] Handled serverError (500) but cannot output into desired format (NULL): 'Unable to connect to tls://ratoncitos.p4g.club:443. Error: Connection timed out'
POST /main/remotefollowsub] ServerErrorAction: 500 Unable to connect to tls://ratoncitos.p4g.club:443. Error: Connection timed out</code>
First of all, I've pushed some small fixes to ActivityPub subscription related code, so you might want to update your test instances. The RemoteFollow plugin translation problems were also fixed.
In relation to this issue, I was able to correctly remote-follow users from these v2 instances:
ratoncitos.p4g.club
social.hackersatporto.com
@aab, khp.ignorelist.com seems to be the only one causing problems. I found that, for some reason, the inbox in that instance is not signing the requests, causing "Invalid signature" in my side. This happens with both the existing local users. I don't really understand why this is happening, but I'll be discussing with @diogo since he has better understanding of HTTP signatures. In any case, could you update this instance with the new fixes? (Sanity checking, there's one relevant small fix)
Hello @ziggys, @aab.
First of all, I've pushed some small fixes to ActivityPub subscription related code, so you might want to update your test instances. The RemoteFollow plugin translation problems were also fixed.
In relation to this issue, I was able to correctly remote-follow users from these v2 instances:
+ ratoncitos.p4g.club
+ social.hackersatporto.com
@aab, khp.ignorelist.com seems to be the only one causing problems. I found that, for some reason, the inbox in that instance is not signing the requests, causing "Invalid signature" in my side. This happens with both the existing local users. I don't really understand why this is happening, but I'll be discussing with @diogo since he has better understanding of HTTP signatures. In any case, could you update this instance with the new fixes? (Sanity checking, there's one relevant small fix)
@aab can you please try following tenma@social.hackersatporto.com? Does it fail? If so, do you get the same errors provided here? Does the following message appears? ActivityPub Inbox: HTTP Signature: Invalid signature.
Unfortunately the problem still persists.
@aab can you please try following tenma@social.hackersatporto.com? Does it fail? If so, do you get the same errors provided [here](https://notabug.org/diogo/gnu-social/issues/70#issuecomment-15625)? Does the following message appears? `ActivityPub Inbox: HTTP Signature: Invalid signature.`
@aab yes you do, I've used that handle too and I'm able to follow ziggys.
I'm still not able to follow you back from hackersatporto, same invalid signature error. In any case, I believe it is safe to assume that the root of this problem is not in the v2 version of GS since me, diogo and apparently ziggys can correctly federate with these and even other software instances. Furthermore, since the HTTP signatures are known to be working, the invalid signature error I'm getting from your instance is most likely caused by the Connection timed out problem from your side. This message seems to suggest network issues from your server.
Until further developments, and since I can't really reproduce the errors you're experiencing, I'll close this issue for now.
@aab yes you do, I've used that handle too and I'm able to follow ziggys.
I'm still not able to follow you back from hackersatporto, same invalid signature error. In any case, I believe it is safe to assume that the root of this problem is not in the v2 version of GS since me, diogo and apparently ziggys can correctly federate with these and even other software instances. Furthermore, since the HTTP signatures are known to be working, the invalid signature error I'm getting from your instance is most likely caused by the `Connection timed out` problem from your side. This message seems to suggest network issues from your server.
Until further developments, and since I can't really reproduce the errors you're experiencing, I'll close this issue for now.
tenma
Hi, I'm getting this error when trying to follow an account from a gnusocial instance running nightly.
Scenario:
Gnusocial version: 2.0-dev (nightly) - RemoteFollow plugin active
Following remote accounts is posible for some mastodon, pleroma and gnusocial v1.20.x instances.
When confirmation button pressed on following remote account from gnusocial v2.0-dev (nightly) account, next error is received in web-browser: "Internal Server Error. An unknown error occurred."
nginx access and error logs don't show this error
This is the log from web-console (some data is ofuscated or omitted for privacy reasons)
In case it is useful, this is what i get when trying to follow you from another v2 node:
POST /main/remotefollowsub] HTTPClient: HTTP POST https://ratoncitos.p4g.club/inbox.json - 400 Bad RequestPOST /main/remotefollowsub] Handled serverError (500) but cannot output into desired format (NULL): 'Unable to connect to tls://ratoncitos.p4g.club:443. Error: Connection timed out'
POST /main/remotefollowsub] ServerErrorAction: 500 Unable to connect to tls://ratoncitos.p4g.club:443. Error: Connection timed out
Hello @ziggys, @aab.
First of all, I've pushed some small fixes to ActivityPub subscription related code, so you might want to update your test instances. The RemoteFollow plugin translation problems were also fixed.
In relation to this issue, I was able to correctly remote-follow users from these v2 instances:
@aab, khp.ignorelist.com seems to be the only one causing problems. I found that, for some reason, the inbox in that instance is not signing the requests, causing "Invalid signature" in my side. This happens with both the existing local users. I don't really understand why this is happening, but I'll be discussing with @diogo since he has better understanding of HTTP signatures. In any case, could you update this instance with the new fixes? (Sanity checking, there's one relevant small fix)
@tenma, @aab has a special branch for him due to some temporary server constraints he has. Just update his branch so that he can re-test :)
I just upgraded; even though i see the same behaviour with "ratoncitos", maybe now you can try...
By the way, i follow @diogo on the test node.
Unfortunately the problem still persists.
@aab can you please try following tenma@social.hackersatporto.com? Does it fail? If so, do you get the same errors provided here? Does the following message appears?
ActivityPub Inbox: HTTP Signature: Invalid signature.I just upgraded; Still not able to follow @aab.
Successfully followed @tenma and @diogo from social.hackersatporto.com
@temma I just followed you just fine, no error message. Am i using the right handle for ziggys - https://ratoncitos.p4g.club/ziggys ?
@aab yes you do, I've used that handle too and I'm able to follow ziggys.
I'm still not able to follow you back from hackersatporto, same invalid signature error. In any case, I believe it is safe to assume that the root of this problem is not in the v2 version of GS since me, diogo and apparently ziggys can correctly federate with these and even other software instances. Furthermore, since the HTTP signatures are known to be working, the invalid signature error I'm getting from your instance is most likely caused by the
Connection timed outproblem from your side. This message seems to suggest network issues from your server.Until further developments, and since I can't really reproduce the errors you're experiencing, I'll close this issue for now.