# TestNet BlockExplorer Dependency

**URL:** https://community.blockcerts.org/t/testnet-blockexplorer-dependency/1963
**Category:** Technical
**Created:** [June 12, 2019, 2:58pm UTC](https://community.blockcerts.org/t/testnet-blockexplorer-dependency/1963 "2019-06-12T14:58:57Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Fernando](https://avatars.discourse-cdn.com/v4/letter/f/779978/32.png) [@Fernando](https://community.blockcerts.org/u/Fernando)
#### Post date: [June 12, 2019, 2:58pm UTC](https://community.blockcerts.org/t/testnet-blockexplorer-dependency/1963/1 "2019-06-12T14:58:57Z")

</div>

Hello,

I’d like to understand the dependency to issue a certificate in relation with the testnet.blockexplorer.

Since 3 ou 4 days ago, I can’t issue a new certificate in Bitcoin TestNet, due that error: **[testnet.blockexplorer.com](http://testnet.blockexplorer.com) | 521: Web server is down**.

It’s mean that testnet bitcoin is down ? I don’t understand , because I’m able to generate credit from Faucet to my public address… so in my mind it can’t be off… to transfer credit…

Could someone help me to understand this ?

WARNING - Your app is configured to skip the wifi check when the USB is plugged in. Read the documentation to ensure this is what you want, since this is less secure  
INFO - This run will try to issue on the bitcoin\_testnet chain  
INFO - Set cost constants to recommended\_tx\_fee=0.000600,min\_per\_output=0.000028,satoshi\_per\_byte=250  
INFO - Processing 1 certificates  
INFO - Processing 1 certificates under work path=/ufp/tmp  
INFO - Total cost will be 133500 satoshis  
INFO - Starting finalizable signer  
WARNING - app is configured to skip the wifi check when the USB is plugged in. Read the documentation to ensure this is what you want, since this is less secure  
INFO - Stopping finalizable signer  
WARNING - app is configured to skip the wifi check when the USB is plugged in. Read the documentation to ensure this is what you want, since this is less secure  
INFO - here is the op\_return\_code data: be2eaa1d0e526b2532ba76c4b476835639863dd7681958c093997c162f7908b9  
INFO - Unsigned hextx=0100000001d3bef20a90c986b69488d3025180a7b3b43b194631fc249bf02a75459c7dec630000000000ffffffff02e0570e00000000001976a91407317edb86a2fc4226bf182d544d55e591882b1988ac0000000000000000226a20be2eaa1d0e526b2532ba76c4b476835639863dd7681958c093997c162f7908b900000000  
INFO - Preparing tx for signing  
INFO - Starting finalizable signer  
WARNING - app is configured to skip the wifi check when the USB is plugged in. Read the documentation to ensure this is what you want, since this is less secure  
INFO - Stopping finalizable signer  
WARNING - app is configured to skip the wifi check when the USB is plugged in. Read the documentation to ensure this is what you want, since this is less secure  
INFO - The actual transaction size is 235 bytes  
INFO - Signed hextx=0100000001d3bef20a90c986b69488d3025180a7b3b43b194631fc249bf02a75459c7dec63000000006b483045022100c628ed9fa18b9415903d67c7d686ef41991fc76658f686883ad50c165ef5897b02201121031a2c076c6ba70779c8172a17450867f399bded0cc68aa574a2f8f12b4b0121020dbf838b8c19f2863caaf908b24f7d902599fbd9339fcf12b5f3c8f8fba1f2e3ffffffff02e0570e00000000001976a91407317edb86a2fc4226bf182d544d55e591882b1988ac0000000000000000226a20be2eaa1d0e526b2532ba76c4b476835639863dd7681958c093997c162f7908b900000000  
INFO - Signed hextx=0100000001d3bef20a90c986b69488d3025180a7b3b43b194631fc249bf02a75459c7dec63000000006b483045022100c628ed9fa18b9415903d67c7d686ef41991fc76658f686883ad50c165ef5897b02201121031a2c076c6ba70779c8172a17450867f399bded0cc68aa574a2f8f12b4b0121020dbf838b8c19f2863caaf908b24f7d902599fbd9339fcf12b5f3c8f8fba1f2e3ffffffff02e0570e00000000001976a91407317edb86a2fc4226bf182d544d55e591882b1988ac0000000000000000226a20be2eaa1d0e526b2532ba76c4b476835639863dd7681958c093997c162f7908b900000000  
INFO - verifying op\_return value for transaction  
INFO - verified OP\_RETURN  
WARNING - Caught exception trying provider \<bound method BlockrIOBroadcaster.broadcast\_tx of \<cert\_issuer.blockchain\_handlers.bitcoin.connectors.BlockrIOBroadcaster object at 0x7f0c533459b0\>\>. Trying another. Exception=Expecting value: line 1 column 1 (char 0)  
ERROR - Error broadcasting the transaction through the BlockExplorer API. Error msg:

 testnet.blockexplorer.com | 521: Web server is down body{margin:0;padding:0}

# Error521Ray ID: 4e5ca26dcfe1cf64 • 2019-06-12 14:49:58 UTC

## Web server is down

You
### Browser
Working

Ashburn
### Cloudflare
Working

testnet.blockexplorer.com
### Host
Error

## What happened?

The web server is not returning a connection. As a result, the web page is not displaying.

## What can I do?

##### If you are a visitor of this website:

Please try again in a few minutes.

##### If you are the owner of this website:

Contact your hosting provider letting them know your web server is not responding. [Additional troubleshooting information](https://support.cloudflare.com/hc/en-us/articles/200171916-Error-521).

Cloudflare Ray ID: **4e5ca26dcfe1cf64** •Your IP: 13.72.69.230•Performance & security by [Cloudflare](https://www.cloudflare.com/5xx-error-landing?utm_source=error_footer)

WARNING - Caught exception trying provider \<bound method BlockExplorerBroadcaster.broadcast\_tx of \<cert\_issuer.blockchain\_handlers.bitcoin.connectors.BlockExplorerBroadcaster object at 0x7f0c53345860\>\>. Trying another. Exception=

---

<div class="post-metadata">

### Author: ![ecast96](https://avatars.discourse-cdn.com/v4/letter/e/ec9cab/32.png) [@ecast96](https://community.blockcerts.org/u/ecast96)
#### Post date: [June 14, 2019, 2:56pm UTC](https://community.blockcerts.org/t/testnet-blockexplorer-dependency/1963/2 "2019-06-14T14:56:27Z")

</div>

I’m getting the same thing.

---

<div class="post-metadata">

### Author: ![Fernando](https://avatars.discourse-cdn.com/v4/letter/f/779978/32.png) [@Fernando](https://community.blockcerts.org/u/Fernando)
#### Post date: [June 14, 2019, 8:10pm UTC](https://community.blockcerts.org/t/testnet-blockexplorer-dependency/1963/3 "2019-06-14T20:10:41Z")

</div>

I think if it’s really down, nobody is issuing certificate in testnet bitcoin, right ?

If my afirmation is true, maybe the cert-issuer should allow to setup a differente blockexplorer in config.ini…

Att,  
Fernando.

---

<div class="post-metadata">

### Author: ![ecast96](https://avatars.discourse-cdn.com/v4/letter/e/ec9cab/32.png) [@ecast96](https://community.blockcerts.org/u/ecast96)
#### Post date: [June 14, 2019, 8:34pm UTC](https://community.blockcerts.org/t/testnet-blockexplorer-dependency/1963/4 "2019-06-14T20:34:47Z")

</div>

I got it working after updating my cert-issuer folder to the latest from the GitHub repo. It still fails a couple times at the same part of the process but it eventually goes through. I was then able to look up the Tx id to verify it was issued.

have you tried updating to the latest version?

---

<div class="post-metadata">

### Author: ![Fernando](https://avatars.discourse-cdn.com/v4/letter/f/779978/32.png) [@Fernando](https://community.blockcerts.org/u/Fernando)
#### Post date: [June 15, 2019, 5:33pm UTC](https://community.blockcerts.org/t/testnet-blockexplorer-dependency/1963/5 "2019-06-15T17:33:34Z")

</div>

I updated and tested again, and it work !

Thank you @ecast96