#242 Gnusocial.no - activitypub issues

Closed
opened 2 years ago by stigatle · 6 comments
stigatle commented 2 years ago

Hi, I recently got https://gnusocial.no over on nightly, activitypub does not seem to work as it should (problems with notices not arriving and various other issues like that). There is some more info here: https://nu.federati.net/conversation/2526658#notice-3367898

So my question now is - how can I get this resolved? In the thread above the issue is mentioned that it could be that https://gnusocial.no has been reinstalled as a fresh install. And I know I did that my self at least two times during previous testing. I'm not sure if the previous owner of the domain ran activitipub - so I cannot answer that, I bought the domain after it went up for sale, then installed gnusocial (stable) - then tested nightly a couple of times before I was able to make it run properly on my server. The previous owner did not want to give me access to the old site to continue running it - that's why I had to do a fresh install from scratch.

Is there anything I can do so that servers accepts my server as not a impostor server? (If that's the cause of the issues we're seeing?).

Hi, I recently got https://gnusocial.no over on nightly, activitypub does not seem to work as it should (problems with notices not arriving and various other issues like that). There is some more info here: https://nu.federati.net/conversation/2526658#notice-3367898 So my question now is - how can I get this resolved? In the thread above the issue is mentioned that it could be that https://gnusocial.no has been reinstalled as a fresh install. And I know I did that my self at least two times during previous testing. I'm not sure if the previous owner of the domain ran activitipub - so I cannot answer that, I bought the domain after it went up for sale, then installed gnusocial (stable) - then tested nightly a couple of times before I was able to make it run properly on my server. The previous owner did not want to give me access to the old site to continue running it - that's why I had to do a fresh install from scratch. Is there anything I can do so that servers accepts my server as not a impostor server? (If that's the cause of the issues we're seeing?).
Diogo Cordeiro commented 2 years ago
Owner

I think the issue is just some webserver misconfiguration.

This link works: https://social.hackersatporto.com/.well-known/webfinger?resource=acct%3Adiogo%40social.hackersatporto.com

This link doesn't (and should, it's why it's failing): https://gnusocial.no/.well-known/webfinger?resource=acct%3Asigatle%40gnusocial.no

This link does for the sake of curiosity: https://gnusocial.no/.well-known/webfinger?resource=stigatle@gnusocial.no

Relevant debug logs from my instance:

2021-05-31 20:02:23 LOG_INFO: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] ActivityPubPlugin: Checking webfinger person 'sigatle@gnusocial.no'
2021-05-31 20:02:23 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] Performing discovery for "acct:sigatle@gnusocial.no" (normalized "acct:sigatle@gnusocial.no")
2021-05-31 20:02:23 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD discovery method for 'acct:sigatle@gnusocial.no': LRDDMethod_WebFinger
2021-05-31 20:02:23 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] HTTPClient: HTTP GET https://gnusocial.no/.well-known/webfinger?resource=acct%3Asigatle%40gnusocial.no - 403 Forbidden
2021-05-31 20:02:23 LOG_INFO: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] 'LRDDMethod_WebFinger': Failed for 'acct:sigatle@gnusocial.no': 'Unexpected HTTP status code.'
2021-05-31 20:02:23 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD discovery method for 'acct:sigatle@gnusocial.no': LRDDMethod_HostMeta
2021-05-31 20:02:23 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] Checking URL against blacklist: 'https://gnusocial.no/.well-known/host-meta'
2021-05-31 20:02:24 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] HTTPClient: HTTP GET https://gnusocial.no/.well-known/host-meta - 403 Forbidden
2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD could not load resource descriptor: https://gnusocial.no/.well-known/host-meta (Unexpected HTTP status code.)
2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] Checking URL against blacklist: 'http://gnusocial.no/.well-known/host-meta'
2021-05-31 20:02:24 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] HTTPClient: HTTP GET http://gnusocial.no/.well-known/host-meta - 404 Not Found
2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD could not load resource descriptor: http://gnusocial.no/.well-known/host-meta (Unexpected HTTP status code.)
2021-05-31 20:02:24 LOG_INFO: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] 'LRDDMethod_HostMeta': Failed for 'acct:sigatle@gnusocial.no': 'Unable to retrieve resource descriptor links.'
2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD discovery method for 'acct:sigatle@gnusocial.no': LRDDMethod_LinkHeader
2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] Checking URL against blacklist: 'acct:sigatle@gnusocial.no'
2021-05-31 20:02:24 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] HTTPClient: HTTP HEAD acct:sigatle@gnusocial.no - HTTP_Request2 needs an absolute HTTP(S) request URL, 'acct:sigatle@gnusocial.no' given
2021-05-31 20:02:24 LOG_INFO: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] 'LRDDMethod_LinkHeader': Failed for 'acct:sigatle@gnusocial.no': 'HTTP_Request2 needs an absolute HTTP(S) request URL, \'acct:sigatle@gnusocial.no\' given'
2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD discovery method for 'acct:sigatle@gnusocial.no': LRDDMethod_LinkHTML
2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] Checking URL against blacklist: 'acct:sigatle@gnusocial.no'
2021-05-31 20:02:24 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] HTTPClient: HTTP GET acct:sigatle@gnusocial.no - HTTP_Request2 needs an absolute HTTP(S) request URL, 'acct:sigatle@gnusocial.no' given
2021-05-31 20:02:24 LOG_INFO: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] 'LRDDMethod_LinkHTML': Failed for 'acct:sigatle@gnusocial.no': 'HTTP_Request2 needs an absolute HTTP(S) request URL, \'acct:sigatle@gnusocial.no\' given'
2021-05-31 20:02:24 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] ActivityPubPlugin: Webfinger check failed: Not a valid WebFinger address.

Everything else looks fine, well, maybe you'd like to properly configure the pretty URLs. They seem to be enabled on the server conf bug not set as default in GS's config.

I think the issue is just some webserver misconfiguration. This link works: https://social.hackersatporto.com/.well-known/webfinger?resource=acct%3Adiogo%40social.hackersatporto.com This link doesn't (and should, **it's why it's failing**): https://gnusocial.no/.well-known/webfinger?resource=acct%3Asigatle%40gnusocial.no This link does for the sake of curiosity: https://gnusocial.no/.well-known/webfinger?resource=stigatle@gnusocial.no Relevant debug logs from my instance: ``` 2021-05-31 20:02:23 LOG_INFO: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] ActivityPubPlugin: Checking webfinger person 'sigatle@gnusocial.no' 2021-05-31 20:02:23 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] Performing discovery for "acct:sigatle@gnusocial.no" (normalized "acct:sigatle@gnusocial.no") 2021-05-31 20:02:23 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD discovery method for 'acct:sigatle@gnusocial.no': LRDDMethod_WebFinger 2021-05-31 20:02:23 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] HTTPClient: HTTP GET https://gnusocial.no/.well-known/webfinger?resource=acct%3Asigatle%40gnusocial.no - 403 Forbidden 2021-05-31 20:02:23 LOG_INFO: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] 'LRDDMethod_WebFinger': Failed for 'acct:sigatle@gnusocial.no': 'Unexpected HTTP status code.' 2021-05-31 20:02:23 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD discovery method for 'acct:sigatle@gnusocial.no': LRDDMethod_HostMeta 2021-05-31 20:02:23 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] Checking URL against blacklist: 'https://gnusocial.no/.well-known/host-meta' 2021-05-31 20:02:24 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] HTTPClient: HTTP GET https://gnusocial.no/.well-known/host-meta - 403 Forbidden 2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD could not load resource descriptor: https://gnusocial.no/.well-known/host-meta (Unexpected HTTP status code.) 2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] Checking URL against blacklist: 'http://gnusocial.no/.well-known/host-meta' 2021-05-31 20:02:24 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] HTTPClient: HTTP GET http://gnusocial.no/.well-known/host-meta - 404 Not Found 2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD could not load resource descriptor: http://gnusocial.no/.well-known/host-meta (Unexpected HTTP status code.) 2021-05-31 20:02:24 LOG_INFO: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] 'LRDDMethod_HostMeta': Failed for 'acct:sigatle@gnusocial.no': 'Unable to retrieve resource descriptor links.' 2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD discovery method for 'acct:sigatle@gnusocial.no': LRDDMethod_LinkHeader 2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] Checking URL against blacklist: 'acct:sigatle@gnusocial.no' 2021-05-31 20:02:24 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] HTTPClient: HTTP HEAD acct:sigatle@gnusocial.no - HTTP_Request2 needs an absolute HTTP(S) request URL, 'acct:sigatle@gnusocial.no' given 2021-05-31 20:02:24 LOG_INFO: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] 'LRDDMethod_LinkHeader': Failed for 'acct:sigatle@gnusocial.no': 'HTTP_Request2 needs an absolute HTTP(S) request URL, \'acct:sigatle@gnusocial.no\' given' 2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] LRDD discovery method for 'acct:sigatle@gnusocial.no': LRDDMethod_LinkHTML 2021-05-31 20:02:24 LOG_DEBUG: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] Checking URL against blacklist: 'acct:sigatle@gnusocial.no' 2021-05-31 20:02:24 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] HTTPClient: HTTP GET acct:sigatle@gnusocial.no - HTTP_Request2 needs an absolute HTTP(S) request URL, 'acct:sigatle@gnusocial.no' given 2021-05-31 20:02:24 LOG_INFO: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] 'LRDDMethod_LinkHTML': Failed for 'acct:sigatle@gnusocial.no': 'HTTP_Request2 needs an absolute HTTP(S) request URL, \'acct:sigatle@gnusocial.no\' given' 2021-05-31 20:02:24 LOG_ERR: [social.hackersatporto.com:2794968.52285cc0 POST /notice/new] ActivityPubPlugin: Webfinger check failed: Not a valid WebFinger address. ``` Everything else looks fine, well, maybe you'd like to properly configure the pretty URLs. They seem to be enabled on the server conf bug not set as default in GS's config.
lnxw37 commented 2 years ago

Subscribing to this, in case there's more to it.

Subscribing to this, in case there's more to it.
aab commented 2 years ago

@stigatle Just in case you need a hand with this:

1) Pretty URLs:

  • Read and apply https://notabug.org/diogo/gnu-social/src/nightly/INSTALL.md#fancy-urls. As you are using Apache, just make sure .htaccess is in /public (and edit if needed, but i don't think you do).
  • Include this in your config.php: $config['site']['fancy'] = true;
  • I can't remember it it is needed, but no harm in checking if "Facy URLs" is on in Admin-Routes.

2) Webserver misconfiguration noted by @diogo: try the settings commented on #238

I'm also using Apache in one of my hosts, just ask if you need anything.

@stigatle Just in case you need a hand with this: 1) Pretty URLs: - Read and apply https://notabug.org/diogo/gnu-social/src/nightly/INSTALL.md#fancy-urls. As you are using Apache, just make sure .htaccess is in /public (and edit if needed, but i don't think you do). - Include this in your config.php: $config['site']['fancy'] = true; - I can't remember it it is needed, but no harm in checking if "Facy URLs" is on in Admin-Routes. 2) Webserver misconfiguration noted by @diogo: try the settings commented on https://notabug.org/diogo/gnu-social/issues/238#issuecomment-25766 I'm also using Apache in one of my hosts, just ask if you need anything.
stigatle commented 2 years ago
Poster

Thank you for the feedback. I have the .htaccess file in public.

If you go directly to this url: https://gnusocial.no/main/register You'll see the 'short version' of url is working. However when I then browse the site (timelines etc) it reverts back to include the full url like this: https://gnusocial.no/index.php/main/register

I have disable everything custom I can see in my apache config to make it as clean as possible, and have not figured out what's going wrong yet. But as mentioned higher up - the culprit is this issue.

Thank you for the feedback. I have the .htaccess file in public. If you go directly to this url: https://gnusocial.no/main/register You'll see the 'short version' of url is working. However when I then browse the site (timelines etc) it reverts back to include the full url like this: https://gnusocial.no/index.php/main/register I have disable everything custom I can see in my apache config to make it as clean as possible, and have not figured out what's going wrong yet. But as mentioned higher up - the culprit is this issue.
Diogo Cordeiro commented 2 years ago
Owner

@stigatle To fix the fancy urls issue, it should be enough to add $config['site']['fancy'] = true; to the end of your config.php (as noted by @aab).

That won't solve the webfinger issue, that one has smth to do with how your webserver is parsing the urls...

@stigatle To fix the fancy urls issue, it should be enough to add `$config['site']['fancy'] = true;` to the end of your `config.php` (as noted by @aab). That won't solve the webfinger issue, that one has smth to do with how your webserver is parsing the urls...
stigatle commented 2 years ago
Poster

Hi again, sorry for answering late - and for bringing this issue up again. But I have enabled fancy url in the settings, and added the .htaccess file in public - but the issue remains.

Is it apache that's causing this? I'm trying to find a solution - but nothing that I've tried has succeeded in fixing it - and it seems to affect various things on the site as well (some people are reporting that the site some times is unresponsive when they do certain actions on the site, and I suspect what has been mentioned here is causing that. So I'm really want to get this sorted somehow.

There is some more info from the user here: https://gnusocial.no/index.php/conversation/966#notice-2068

Hi again, sorry for answering late - and for bringing this issue up again. But I have enabled fancy url in the settings, and added the .htaccess file in public - but the issue remains. Is it apache that's causing this? I'm trying to find a solution - but nothing that I've tried has succeeded in fixing it - and it seems to affect various things on the site as well (some people are reporting that the site some times is unresponsive when they do certain actions on the site, and I suspect what has been mentioned here is causing that. So I'm really want to get this sorted somehow. There is some more info from the user here: https://gnusocial.no/index.php/conversation/966#notice-2068
Sign in to join this conversation.
No Milestone
No assignee
4 Participants
Loading...
Cancel
Save
There is no content yet.