andyrozman
commented
1 year ago Ok. So almost possitive report... I changed my settings to base one (just listening on port 8444, without UPnP which doesn;t work anymore), I can see that I am connected to several clients, but sending of message is still stuck "Waiting for their encryption key. Will request it again soon.". And this happens with echo server, which should work always, right (BM-2cWoG7fKafmVbfeMh8U2mRgix6eTuGSQCK)? I am getting back heartbeat from TimeService so I know that some communication is working...
There are some exceptions I can see: uncaptured python exception (when doing handshape) and there is Proof of Work exception (no more data there).
I am still in the dark if this technology is even still being used... Forum is dead, documentation is old... This is why I used this as means of communication.
Github has this nice feature called "Discussions", could you please enable it and document it on Wiki, as alternate to forum that is no longer working...
I am testing with AppImage from here https://appimage.bitmessage.org/releases/20230116/ , I also tried last image from https://artifacts.bitmessage.at/appimage/17629/, which worked ok, but my "indicator" icon is missing from this build.
PLEASE OPEN DISCUSSIONS here on GitHub.
Hi ! I am using latest Appimage (which is from January) on Ubuntu 22.04 (tried to build myself but failed - missing deps). So I can run it from AppImage, but I can't get it to green. So I use port 8144 (which I configured on router to passthrough to my Ip address) and I have Socks 5 configured on localhost: 9150). All my other software (like qbttorrent) manages to negotiate with my Router with UpNp, but not Bit meesage, which is why I added static route to my router. I ahve tor browser running at same time, with hope that this will work...
I am not sure if the problem is with my app image or with my network configuration...
I am total newbie with Tor and PyBitMessage, so I might be doing some very basic mistake... Any pointers to right direction, would be very welcome.