Fritter hangs trying to connect to self

[Michael-S]

I'm not sure if this is a Fritter issue, a broader Beaker Browser bug, or a Beaker Browser on Linux bug. I opened firewall port 3282 on my firewall and on the VM running Beaker Browser and had the firewall redirect incoming traffic to 192.168.1.19 (the IP of the VM) so that anything I post on Fritter is available through dat to the world. But now when I open any link inside Fritter, the content never loads and my debug log is filled with these messages:

error (0ms) id=754371 type=tcp host=::ffff:192.168.1.19:3282 error=Error: Remote sent invalid feed message
closing connection (2ms) id=754371 type=tcp host=::ffff:192.168.1.19:3282
closing connection (5002ms) id=754363 type=utp host=0.0.0.0:3282
error (7505ms) id=754358 type=tcp host=::ffff:192.168.1.19:3282 error=Error: Remote timed out
closing connection (7507ms) id=754358 type=tcp host=::ffff:192.168.1.19:3282
and then it starts over
error (4ms) id=754372 type=tcp host=::ffff:192.168.1.19:3282 error=Error: Remote sent invalid feed message

[Michael-S]

Wait, now I'm thinking this might be a result of issue #17 - maybe Beaker is contacting itself for Fritter updates because it incorrectly has me as the source of some messages. I did see "replying to you" a few times for things I did not write.

[pfrazee]

Hey @Michael-S. I haven't tried to configure firewall rules like you're doing, so I don't have any advice for you, but it is definitely clear that connections on the dat network are failing. #17 shouldn't be related.