`Subscribe Pending` shown for all federated subscribes

[dessalines]

@Nutomic I've noticed this exists for all federated subscribes, even ones that happened in the past.

[hanubeki]

Cancelling "pending" subscription and re-subscribe worked for me, except for narwhal.city one (which is lotide)

[informapirata]

L'annullamento dell'abbonamento "in sospeso" e il nuovo abbonamento hanno funzionato per me, ad eccezione di narwhal.city one (che è lotide)

With Mastodon and Pleroma the problem is solved by removing the follow and putting it back on again. But with Misskey it doesn't seem to work

[Nutomic]

These are actually marked as pending in the db now. Which is strange because this is the only recent db migration that touches the column, and it sets pending = false, not true.

[dessalines]

The only place I can see in the code where it sets it to true, is here, which seems correct.

Maybe there used to be an issue with accepting a follow, and the UI didn't reflect this for some reason?

Either way, I'm not sure if the correct solution is to do a DB migration to correct those, or ask people to re-follow all their federated communities.

[Nutomic]

Maybe an old Lemmy version used to write subscribed: None in case of success.

I guess its best to ask people to refollow if it bothers them, otherwise we risk causing even more problems.

[JackFromWisconsin]

I guess its best to ask people to refollow if it bothers them, otherwise we risk causing even more problems.

Does "Subscribe Pending" still act as a normal subscription?

[Nutomic]

If it worked before the upgrade then it should still work fine. Lemmy is only displaying the status wrong.

[SiskoUrso]

Just started an instance today and having this same issue. Is this only graphical issue and you are indeed subscribed?

[Nutomic]

@SiskoUrso If its a new instance then that suggests that federation isnt working properly. Go through the troubleshooting steps from documentation.

https://join-lemmy.org/docs/en/administration/troubleshooting.html#federation

[SiskoUrso]

@SiskoUrso If its a new instance then that suggests that federation isnt working properly. Go through the troubleshooting steps from documentation.

https://join-lemmy.org/docs/en/administration/troubleshooting.html#federation

Guess I'm not sure where its going wrong, testing with the commands in the Federation troubleshooting seemed to all return a valid response.

I am using NGINX Proxy Manager , I have custom locations setup for /api, /pictrs, /feeds, /nodeinfo, /.well-known all pointing to the correct ip and port 8536. Looked over the nginx template provided in another post but not sure how to use that in NPM.

Everything else seems to be working except this , as far as I can tell.

Any guidance is appreciated.

[Nutomic]

Check the server logs for any errors while following a remote community. You can grep for the domain name of the other instance.

If you can post in remote communities and these posts show up normally on the other instance, then the problem might be that other instances cant deliver their actions to your instance. In this case the other instance should log some errors so you need to contact the admin.

[Zetaphor]

I'm also experiencing this on a brand new instance. Nearly all of the communities I've subscribed to are showing as pending, the total number of comments isn't matching in my instance and theirs, and I was able to get valid JSON from all of the troubleshooting steps.

I'm able to subscribe to one community on an instance, but getting subscription pending for another community on the same instance.

I've checked my logs and am not seeing any errors. I'm also not running a reverse proxy, I just setup with ansible as described in the wiki

[NettoHikari]

I'm in the same boat. No errors in the logs, but "Subscribe Pending" anyway. I also use NGINX Proxy Manager, if that's necessary to point out.

[verymilan]

idk i keep having this on the big ones: lemmy.ml and beehaw (when i try to sub to a tchncs community, not the other way around) – when i try to do the same thing on feddit it almost never happens