gts 0.12.1 : some of my toots does not appearing on my followers timelines

[kuspoes]

from my followers (mastodon users), they are complaining that some of my toots doesnt show up on their timelines after 0.12.1. I've checked the log messages and get a lot of errors like this :

msg="error dereferencing collection page 
 tls: failed to verify certificate: x509: certificate signed by unknown authority"

I have using nginx and follow this guide https://docs.gotosocial.org/en/latest/getting_started/reverse_proxy/nginx/ to handle letsencrypt. Is there any guide to fix this problem? thanks

[tsmethurst]

Do you get those error messages when you've just posted something? Ie., if you tail your instance logs as you're making a post, is that the only issue you see? Or are there any other pertinent logs?

[tsmethurst]

Also, does this occur with multiple instances? Or just one instance? Is it only Mastodon instances, or other instance types too?

[kuspoes]

Also, does this occur with multiple instances? Or just one instance? Is it only Mastodon instances, or other instance types too?

I just create a new post and get this error

ct 31 22:08:21 fdv gotosocial[4868]: timestamp="31/10/2023 22:08:21.703" func=workers.(*Processor).EnqueueClientAPI.func1 level=ERROR requestID=8ej451mb040003w5ag90 msg="error processing client API message: 
CreateStatus: error federating status: CreateStatus: error sending activity *typecreate.ActivityStreamsCreate via outbox https://kauaku.us/users/poes/outbox: 
func1: error delivering to https://mastodon.hidupmanis.studio/inbox: Post \"https://mastodon.hidupmanis.studio/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://fdv.saifulh.web.id/users/s4if/inbox: Post \"https://fdv.saifulh.web.id/users/s4if/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://mas.to/inbox: Post \"https://mas.to/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://fedi.lecturify.net/inbox: Post \"https://fedi.lecturify.net/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://jir.moe/inbox: Post \"https://jir.moe/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://pegelinux.top/inbox: Post \"https://pegelinux.top/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1:
 error delivering to https://yonle.host.lecturify.net/u/yonle/inbox: Post \"https://yonle.host.lecturify.net/u/yonle/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://aus.social/inbox: Post \"https://aus.social/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://fosstodon.org/inbox: Post \"https://fosstodon.org/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://zirk.us/inbox: Post \"https://zirk.us/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://misskey.id/inbox: Post \"https://misskey.id/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://asbestos.cafe/inbox: transport reached max retries\nfunc1: 
error delivering to https://bae.st/inbox: Post \"https://bae.st/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://mastodon.social/inbox: Post \"https://mastodon.social/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://mastodonindonesia.com/inbox: transport reached max retries\nfunc1: 
error delivering to https://mstdn.id/inbox: Post \"https://mstdn.id/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://anakmanis.com/inbox: Post \"https://anakmanis.com/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://ak.independen.top/inbox: Post \"https://ak.independen.top/inbox\": dial tcp: lookup ak.independen.top on 1.1.1.1:53: no such host\nfunc1: 
error delivering to https://fd.s4if.dev/inbox: Post \"https://fd.s4if.dev/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://firefish.social/inbox: Post \"https://firefish.social/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: 
error delivering to https://calckey.world/inbox: Post \"https://calckey.world/inbox\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nfunc1: error delivering to https://ruinafriends.click/inbox: transport reached max retries"

It's look like multiple instances (mastodon, akkoma, pleroma, firefish)

[tsmethurst]

Huh, OK, that's very strange! It's almost like the outgoing requests are being intercepted or something :thinking: Can you give a little more detail about your setup? Is it just running on a VPS, or is it on a homeserver? Do you have an outgoing http proxy configured (https://docs.gotosocial.org/en/latest/advanced/outgoing-proxy/)?

[kuspoes]

youre right, there is something wrong with my firewall. after by passing firewall for a while, create new toot and i get different error

Client.Timeout exceeded while awaiting headers

Do you have an outgoing http proxy configured (https://docs.gotosocial.org/en/latest/advanced/outgoing-proxy/)?

No I dont have this configured

[tsmethurst]

Hmm OK, sounds like there's still something wrong there, but that's definitely progress! It sounds to me like your GtS instance just can't reach the outside world properly for outgoing requests, so I'd suggest checking carefully to make sure that outgoing requests are permitted properly.