Switch to ArdorForum

Before install the extracted zip files you must shutdown all the clients or servers
Here some screenshots how to do it.

First shutdown the nxt client
https://drive.google.com/open?id=0Bxil1u8dt_kvUk5TTGNDOFRobk0

Then remove all these files
https://drive.google.com/open?id=0Bxil1u8dt_kvWEN6aVdsZzdkTWs

Then copy the extracted zip file to that directory
https://drive.google.com/open?id=0Bxil1u8dt_kvRDUtZlJLOVVrbmc

Start your client or server and give it some time to synchronize the missing blocks before you install it on the other nodes.

By the way i'm not so familiar with the Windows platform. But i have download and tested my own blockchain file with Windows 7 under Virtualbox and it works.

Thanks guys, that seems to have done the trick.
My only option was editing nxt-default.properties
4056 blocks left to download.

Welcome aboard 

I downloaded it and I think I put it in the right folder, but Now when I click on the desktop icon I get the following error:


I shared an image of the error to drive dot google dot com/open?id=0BybaofYq9ZXoaUtrdzI5V3pkSkE

Here is what it says:
     org.h2.jdbc.JdhcSQLException: General error: "java.lang.NullPointeException" [50000-196]
     See additional infromation in C:\username\Winuser\AppData\Roaming\NXT\logs\nxt.log

Any Ideas where I went wrong?

First shutdown the nxt client
https://drive.google.com/open?id=0Bxil1u8dt_kvUk5TTGNDOFRobk0

Then remove all these files
https://drive.google.com/open?id=0Bxil1u8dt_kvWEN6aVdsZzdkTWs

Then copy the extracted zip file to that directory
https://drive.google.com/open?id=0Bxil1u8dt_kvRDUtZlJLOVVrbmc

after this all start the nxt client and your done

Quote from: wicket on August 03, 2017, 06:21:45 pm

so frustrating!!!!

Bik_z19 has an alternate backup you can download
I also have backups on ardor.tools for both the NXT and Ardor blockchains

I have but his nxt blockchain is not up to date. (1 month old) 

Minimum Difficulty:   255
Maximum Difficulty:   255
Algorithm SHA256

Mint settings in your nxt-default.properties file

#### MINT ####

# Address of the NXT server to which the mint worker submits its transactions
# (default: localhost).
nxt.mint.serverAddress=localhost

# Use Https when connecting to the server. Note that mint worker accepts any SSL
# certificate as valid, without checking hostname or certificate authority,
# therefore this will not protect you against a man-in-the-middle attack when
# submitting mint transactions.
nxt.mint.useHttps=false

# Specify a mintable currency code.
nxt.mint.currencyCode=LIMBO

# Secret phrase for the minting account, this secret phrase is sent to the host
# specified by nxt.mint.serverAddress therefore do not specify secret phrase of
# an account with lots of funds.
nxt.mint.secretPhrase=your own nxt account password

# Number of units to mint per transaction.
# The minting difficulty grows linearly with the number of units per mint.
nxt.mint.unitsPerMint=1

# The initial nonce used for minting.
# Set to 0 to start with a random nonce.
nxt.mint.initialNonce=0

# Number of concurrency threads used for minting.
# Set to 0 allocate one thread per processor core.
nxt.mint.threadPoolSize=0

# When set to false mint transactions are not submitted when a hash is solved.
# Set this value to true to perform actual minting.
nxt.mint.isSubmitted=true

# When set to false the mint worker will resume operation even in case a mint
# transaction has returned an error response.
nxt.mint.stopOnError=false

Happy minting 

New link did not recognize pass phrase for market. 

 Sounds like it matters to EVERYONE!!!! No forging no market, it's about the flow.

5 devices tried.... Is it the Java? My operating systems and/or browser? This is 99% of devices and operating systems.

Do we need the nxtpi machine? A Vps
 Rasberry pi.

What's your knowledge about Linux?

It is not the best option but here it works fine.
or you can hire a vps. Thats the best option but not the cheapest 

Quote from: wicket on June 27, 2017, 02:36:18 pm

Quote from: MrV777 on June 27, 2017, 02:31:34 pm

Hmm, looks good.  You have NXT running on a server somewhere?  Did you make sure to open the ports if you have a firewall?

It runs on my vps. What ports are necessary to forge?

The peer port necessary to communicate with the network is 7874. If your node has been downloading network data. the port must be already available.

Another reason why your could get a public key error when trying to forge is that the Nxt blockchain is not up to date in your node. If your node has not downloaded yet the block where your first outgoing transaction (or the first incoming transaction with public key announcement) was included, it won't be able to find your public key in the database and return an error.

To see the state of your node from the command line you can do

Code: [Select]

curl "http://127.0.0.1:7876/nxt?requestType=getState"
And then see if the most recent block value in your node, "lastBlockchainFeederHeight", agrees with the latest block height in a block explorer like https://nxtportal.org or https://mynxt.info

Ports are open but can you explain this?
forging allowed goes up and down

https://nxtportal.org/accounts/14723714476777342950

Hmm, looks good.  You have NXT running on a server somewhere?  Did you make sure to open the ports if you have a firewall?

It runs on my vps. What ports are necessary to forge?

I have enough NXT coins. I send 1 NXT to myself, but no forging at all.
The system says i don't have no public key.

Sure i have one

what go wrong?