Block explorer at nuexplorer.ddns.net (superceded by explorer.nubits.com)

I have no idea what the real reason is, but there are at least a few disgruntled former shareholders or people in it for the lulz out there.

The fact that the forums and the explorer are on different hosts and within different IPs with no association other than being part of Nu, and both were attacked at the same time, is suspect.

2 Likes

I’ll add that to my ever-growing list of suspicious stuff.

1 Like

What are the main issue of Nu, from your perspective?

No more interest in cutting weed off? :wink:

I realized the wording is too biblical.
But I d like to help Nu thrive.
Would nt you?

Oh, I do, I do.
Just have a look at all the flaws I pointed out regarding centralization, missing revenue (by design), lack of accounting, trading BTC/NBT instead of NBT/USD etc.
I could go on for some time, but you know all that already if you read my posts.

Isn’t providing information about flaws a good way to improve a project?
At the same time it can be used as test points for future customers and investors.

NuExplorer is stuck on block 1,540,006. Please upgrade. @backpacker


Our new block explorer is available at explorer.nubits.com.

3 Likes

it’s stuck. last block was about 14 hr ago

You must be confused with: https://nuexplorer.ddns.net/ That one is stuck.
explorer.nubits.com is on the right chain since a few days and at the time of posting

thank you for contacting me via email, i apologise for the delay. i’ll update the nud client today.

2 Likes

block explorer has been updated to version 5.2 and fully synched.

2 Likes

@backpacker Certificate expired:

nuexplorer.ddns.net uses an invalid security certificate. The certificate expired on 04/10/17 18:17. The current time is 06/10/17 10:41.

tip for future, you have to reload nginx for renewed certificate to load.

1 Like

They’ve really improved the procedure for certificates! Thought I’d give a short example, but it’s always annoying to find incomplete instructions, so.

Let’s Encrypt with Nginx on Ubuntu 16.04

Install Nginx

apt install -y nginx

Install Certbot

apt-add-repository -y ppa:certbot/certbot
apt update
apt install -y python-certbot-nginx

Configure Nginx

openssl dhparam -out /etc/nginx/dhparam.pem 4096
rm /etc/nginx/sites-enabled/default

Add following to /etc/nginx/conf.d/chat.nubits.com.conf

server {
    server_name  chat.nubits.com;
    listen  80;
    listen  [::]:80;
}
server {
    server_name  chat.nubits.com;
    listen       443 ssl http2;
    listen       [::]:443 ssl http2;

    ssl_dhparam  /etc/nginx/dhparam.pem;

    ssl_ciphers     EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH;
    ssl_ecdh_curve  secp384r1; # Requires nginx >= 1.1.0
    ssl_protocols   TLSv1.2;

    ssl_prefer_server_ciphers  on;
    ssl_session_cache          shared:SSL:10m;
    ssl_session_tickets        off; # Requires nginx >= 1.5.9
    ssl_stapling               on; # Requires nginx >= 1.3.7
    ssl_stapling_verify        on; # Requires nginx >= 1.3.7

    #add_header  Strict-Transport-Security "max-age=63072000; includeSubdomains; preload";
    add_header  X-Content-Type-Options nosniff;
    #add_header  X-Frame-Options DENY;

    resolver          8.8.8.8 8.8.4.4 valid=300s;
    resolver_timeout  5s;
}

Check Nginx configuration

nginx -t

Start Nginx

systemctl enable nginx
systemctl start nginx

Acquire TLS certificate

certbot -n --nginx --agree-tos --no-eff-email --rsa-key-size 4096 --redirect --email team@nubits.com -d chat.nubits.com

Enable automatic renewal

crontab -e

Enter following at bottom.

15 3 * * * /usr/bin/certbot renew --quiet

@backpacker: Thank you for the service you provide. Can you remind us how long your contract is for?

That assumes you are comfortable to use Let’s encrypt certificates.

Which reasons are there to prefer another certificate authority?

http://erik.io/blog/2014/02/03/why-your-ca-rarely-matters/

Browsers on a website with extended validation should display the company providing the verified trust, instead of a string that the CA decides (Subject Organization name).

There’s HPKP to our defense that enables specifying the only CAs to be trusted for that domain. To be precise, the public key of any certificate.

I want to implement HPKP, but obviously it shouldn’t be rushed.

I just noted it as it was not obvious in your post. I don’t care what people use. The only reason would be to have extended verification, which I believe Let’s encrypt doesn’t offer. And whether you want to support Let’s encrypt or another company.

1 Like

Current contract runs out on 5th of June 2018.

I am using certbot renew, but it turns out you have to reload nginx after running it, so I suggest adding that to crontab also.

1 Like

Even when using the Nginx plugin? Good to have in mind.

certbot […] --deploy-hook "systemctl reload nginx"

https://certbot.eff.org/docs/using.html