[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] cannot keep my bridge up



Thank you for this. Is there any way around this? This didn't used to be problem.




Sent with Proton Mail secure email.

------- Original Message -------
On Thursday, December 22nd, 2022 at 7:15 AM, trinity pointard <trinity.pointard@xxxxxxxxx> wrote:


> Hi,
> 
> These lines Toralf references come from the logs you sent. It looks
> like apparmor didn't want obfs4proxy to open some file.
> I'm not sure why obfs4proxy would care about this file, maybe it's
> something the go runtime likes to look at. It does not look fatal
> though.
> 
> Logs also says
> 
> > Dec 20 09:15:27 mxh-HP-Compaq-Pro-6300-SFF Tor[17727]: Your server has not managed to confirm reachability for its ORPort(s) at 100.38.62.232:443.
> > Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
> 
> 
> It looks like your bridge isn't reachable from the internet. Have you
> checked if your firewall accepts incoming connections? If you are on
> an at home installation,
> have you checked if your router NAT is configured to forward that port
> properly. If you are on an at home installation too, is it possible
> you are behind a CG-NAT
> (https://en.wikipedia.org/wiki/Carrier-grade_NAT)?
> 
> Sidenotes: these logs contains your bridge fingerprint and its ip
> address. These are informations you should never share publicly as it
> allows censors to block
> your bridge easily, while being hard to block is supposed to be the
> whole purpose of bridges.
> 
> Regards,
> 
> trinity-1686a
> 
> On Thu, 22 Dec 2022 at 12:47, Anonforpeace via tor-relays
> tor-relays@xxxxxxxxxxxxxxxxxxxx wrote:
> 
> > I'm not sure I understand. Are you showing me more lines of code to add?
> > 
> > Sent from Proton Mail mobile
> > 
> > -------- Original Message --------
> > On Dec 21, 2022, 5:18 AM, Toralf Förster < toralf.foerster@xxxxxx> wrote:
> > 
> > On 12/20/22 15:27, Anonforpeace via tor-relays wrote: > Dec 20 08:55:16 mxh-HP-Compaq-Pro-6300-SFF kernel: [137278.310446] > audit: type=1400 audit(1671544516.974:36): apparmor="DENIED" > operation="open" profile="system_tor" > name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size" pid=17728 > comm="obfs4proxy" requested_mask="r" denied_mask="r" fsuid=128 ouid=0 What about this ? -- Toralf _______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays _______________________________________________
> > tor-relays mailing list
> > tor-relays@xxxxxxxxxxxxxxxxxxxx
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays