Building Cities

[LinmarcusT]

MWD and Jeremy are building the roads so we need to build the cities. I am having a little trouble and would be greatful for a little help. I have gotten as far as installing wordpress and can navigate to my home page but I can't login. Whenever I try it says the connection was reset. Solution? BTW I am trying to install the https plugin but I have to get to the dashboard in order to do so.

Edit: I am getting a namecoin resolution error. and now I cant even get to the login

[cassini]

If you provide us with some more details we might be able to help, e.g.
what OS? (your profile says Linux, but which one?)
what browser version?
where is this "namecoin resolution error" being displayed?

[LinmarcusT]

I am using ubuntu. The error is occuring whenever I try to access my site not my control panel. I am wondering if I have to unpack the extention from the control panal.

2. Activate the plugin through the 'Plugins' menu in WordPress.

when ever I try to do this I get. I can get to my control panel most of the time. The pictrure is what I get when I try to click install plugin

[domob]

Your name d/theseus shows this data for me:

Code: Select all

{"ns":["NS1.QHOSTER.NET","NS2.QHOSTER.NET","NS3.QHOSTER.NET","NS4.QHOSTER.NET"],"fingerprint":"CE:DA:D6:1A:B8:DE:40:1F:EB:77:3D:FE:B9:54:29:87:1F:59:EB:08"}

I believe that FreeSpeechMe doesn't support specifying nameservers, instead you should specify your IP address directly (this makes resolving direct without a further network access and also safer since you don't depend on the nameserver). For instance, you can look at my address d/domob:

Code: Select all

{"ip":"198.50.154.23","map":{"*":"198.50.154.23"},"fingerprint":["4E6CA9CDD335FBF532E8A2B3DA43A1BD05E62DC1","CDCE9B6391057DD67338E20E50C7:FEA37752:a2:f5"]}

(It doesn't currently resolve, either, but that's because my server's IP address changed and I haven't yet updated the dot-bit record.)

[LinmarcusT]

Your name d/theseus shows this data for me:

Code: Select all

{"ns":["NS1.QHOSTER.NET","NS2.QHOSTER.NET","NS3.QHOSTER.NET","NS4.QHOSTER.NET"],"fingerprint":"CE:DA:D6:1A:B8:DE:40:1F:EB:77:3D:FE:B9:54:29:87:1F:59:EB:08"}

I believe that FreeSpeechMe doesn't support specifying nameservers, instead you should specify your IP address directly (this makes resolving direct without a further network access and also safer since you don't depend on the nameserver). For instance, you can look at my address d/domob:

Code: Select all

{"ip":"198.50.154.23","map":{"*":"198.50.154.23"},"fingerprint":["4E6CA9CDD335FBF532E8A2B3DA43A1BD05E62DC1","CDCE9B6391057DD67338E20E50C7:FEA37752:a2:f5"]}

(It doesn't currently resolve, either, but that's because my server's IP address changed and I haven't yet updated the dot-bit record.)

so I am inserting {"ip":"my ip","map":{"*":"my ip"},"fingerprint":

[domob]

Your name d/theseus shows this data for me:

Code: Select all

{"ns":["NS1.QHOSTER.NET","NS2.QHOSTER.NET","NS3.QHOSTER.NET","NS4.QHOSTER.NET"],"fingerprint":"CE:DA:D6:1A:B8:DE:40:1F:EB:77:3D:FE:B9:54:29:87:1F:59:EB:08"}

I believe that FreeSpeechMe doesn't support specifying nameservers, instead you should specify your IP address directly (this makes resolving direct without a further network access and also safer since you don't depend on the nameserver). For instance, you can look at my address d/domob:

Code: Select all

{"ip":"198.50.154.23","map":{"*":"198.50.154.23"},"fingerprint":["4E6CA9CDD335FBF532E8A2B3DA43A1BD05E62DC1","CDCE9B6391057DD67338E20E50C7:FEA37752:a2:f5"]}

(It doesn't currently resolve, either, but that's because my server's IP address changed and I haven't yet updated the dot-bit record.)

so I am inserting {"ip":"my ip","map":{"*":"my ip"},"fingerprint":

The fingerprint part seems already correct with your original value. Instead of the ns field, use ip and map with your IP address, exactly. BTW, if you use Namecoin-Qt, I think you can already configure this in the UI without having to put together the JSON yourself.

[biolizard89]

Your name d/theseus shows this data for me:

Code: Select all

{"ns":["NS1.QHOSTER.NET","NS2.QHOSTER.NET","NS3.QHOSTER.NET","NS4.QHOSTER.NET"],"fingerprint":"CE:DA:D6:1A:B8:DE:40:1F:EB:77:3D:FE:B9:54:29:87:1F:59:EB:08"}

I believe that FreeSpeechMe doesn't support specifying nameservers, instead you should specify your IP address directly (this makes resolving direct without a further network access and also safer since you don't depend on the nameserver). For instance, you can look at my address d/domob:

Code: Select all

{"ip":"198.50.154.23","map":{"*":"198.50.154.23"},"fingerprint":["4E6CA9CDD335FBF532E8A2B3DA43A1BD05E62DC1","CDCE9B6391057DD67338E20E50C7:FEA37752:a2:f5"]}

(It doesn't currently resolve, either, but that's because my server's IP address changed and I haven't yet updated the dot-bit record.)

Nameservers work fine in FreeSpeechMe; the dot-bit.bit domain uses them. However, keep in mind that by using a nameserver instead of an IP address, you are compromising your visitors' privacy and making your site easier to censor. Users who have configured nmcontrol in Private Mode (not the default right now, but this is open to technical discussion) will be shown an error when trying to connect to a .bit domain which uses a nameserver. So an IP address is recommended if possible.

@LinmarcusT: I think the issue you're encountering is due to the known bug with the way WordPress handles the the HTTP requests that FreeSpeechMe sends for non-HTTPS sites. This will be fixed in the future for FreeSpeechMe, but the fix is complicated and may not happen for a while. In the meantime, try using a non-.bit domain to setup WordPress for HTTPS, and then switch to .bit after HTTPS is working.