Namecoin Forum

Found the problem: FoxyProxy for Chrome is broken. Just use Chrome's built-in proxy configuration instead. Works like a charm.

^ I have added a note in https://dot-bit.org/HowToBrowseBitDomains#With_NmcSocks on avoiding FoxyProxy for Chrome and sticking with its built-in proxy configuration. I think this sums up the additional information I needed to make it work.

It seems like it is the Chrome FoxyProxy plugin that is buggy. I just tried with the same plugin for Firefox, and it works perfectly. All .bit domains I've tried so far work. EDIT: I just tried Chrome's built-in proxy configuration, it works as well. So it is FoxyProxy for Chrome that is the culprit...

Is there any command line to test if nmcsocks is working properly? I have nmcsocks (as part of the BamecoinBundle) running. It's listening on port 9055: rune@runescomp:~/Desktop/NamecoinBundleLinux$ netstat -na|grep 9055 tcp 0 0 127.0.0.1:9055 0.0.0.0:* LISTEN but I can't get the FoxyProxy browser a...

I'm experiencing the same problem as lordcirth. Running namecoinBundle.sh: rune@runescomp:~/Desktop/NamecoinBundleLinux$ ./namecoinBundle.sh Launching namecoin... namecoin server starting Launching nnmcsocks... Using namecoin config directory: /home/rune/Desktop/NamecoinBundleLinux/etc Chain proxyin...