Skip to content

Home

Jump to bottom Edit New page
Julian Y edited this page Feb 9, 2018 · 4 revisions

NOTE: This page is a work in progress

Common issues

Please read first!

Wallet or Fusion?

Fusion is a electron application, means its a desktop hybrid application with a web interface. This allows faster development and changes of the Fusion interface and helps with the browser part of Fusion. Therefore some problems can come from electron itself.

Ubiq Wallet is just a Fusion implementation enabled to access a single dapp – the wallet dapp, this is due to missing features in Fusion itself and so that we are able to release earlier. So the wallet is Fusion, in wallet mode.

Please note that Fusion is still in beta and problems can be expected. This guide will help you troubleshooting some of the most common problems. Some steps require the use of the command line or the developer console that Fusion offers. If you need assistance you can ask for help on https://gitter.im/ubiq/fusion.

First step is to make sure you have the latest version of Fusion. Fusion is under active development and new versions contain bugfixes. You can download the latest version here: https://github.com/ubiq/fusion/releases.

If its not a common problem you can look at log files to see if there are errors. It is important to known that the wallet consists of two applications. Fusion, which runs the wallet and a Ubiq node which connects to the network. Communication between the two is done over ipc. A quick scan can be done to determine if the problem is within the Wallet or within the node.

The last part of the node log file can be viewed from Fusion through the top menu bar -> develop -> Show log file. If it contains an error try to search for it on https://github.com/ubiq/fusion/issues?utf8=%E2%9C%93&q=is%3Aissue to see if its already been report and if someone offered a solution.

If there are no errors the next step is to see if there are problems within Fusion. Open the console via the top menu -> develop -> Toggle developer tools -> Wallet UI and look for errors (ignore the "Failed to load resource: net::ERR_FILE_NOT_FOUND" error) and look on the github issue list for simular problems.

If there are none type web3.eth.blockNumber on the console and see if you get the latest block number. If you cannot find the problem create an issue on github and describe as good as possible what you have done and which error you got, preferable with a screenshot and log files included.

Start the node manually

Sometimes its useful to start the node manually to see what its doing:

Stop Fusion and any other Ubiq client, if they are still running. You can start the node manually and see its output on the command line.

Windows

  • Open cmd.exe
  • Navigate to gubiq directory by running cd %APPDATA%\Fusion\binaries\gubiq and look for gubiq.exe
  • Execute the following command: gubiq.exe --cache 1024

Linux

  • Open your terminal of choice
  • Go to .config/Fusion/binaries/gubiq
  • Run ./gubiq --cache 1024

Mac

  • Open Terminal.app
  • Run cd ~/Library/Application\ Support/Fusion/binaries/gubiq
  • Run ./gubiq --cache 1024

You can optionally increase the log level by adding --verbosity 5.

Ubiq is not shown in the wallet

Fusion and Ubiq Wallet displays downloaded data from the blockchain. If you run into this issue, first make sure you are synced with the network. You can also check your balance at a service like UbiqScan.

Sync information are displayed differently in Fusion and Ubiq Wallet, as shown below:

Fusion

Fusion sync

Ubiq Wallet

Ubiq wallet sync

"Your computers time is out of sync!" error

If the time of your computers is deviated the wallet isn't able to connect with the network. The wallet is able to detect if time synchronisation is turned off. Please enable time synchronisation:

Unable to find peers

There are several reasons why the Fusion is not able to connect to the network.

  • Time synchronization problems, please update to the latest version of the wallet.
  • A firewall is preventing access, check the logs of your firewall.
  • A Router doesn't allow NAT or the necessary UDP port 30388, or block other connections made by the Ubiq node.

In some cases users have had succes by starting gubiq manually and add the --nat=none flag.

Fusion is synchronized but is stuck during the last part

Each time the Wallet is started it needs to sync the chain with the network. The first time it needs to download and verify the entire chain which can take a long time. Therefore a smarter and faster solution is used the first time the Wallet is started. It will not download and verify the entire chain but will only download specific parts up to a specific block (latest block - 1024 blocks). After that it will download and process the state of the contracts which can take quite some time. So please wait an let it finish downloading the state, otherwise it would start from scratch again. You can find more details here: https://github.com/ethereum/go-ethereum/pull/1889.

My transaction is not confirmed

There are multiple causes:

  • You lowered the transaction fee. Miners have the option to ignore transaction with a too low fee. It can take a long time before your transaction is included in the block chain. Currently Fusion doesn't provide a solution to resend the transaction with a higher transaction fee.
  • Fusion is not fully synchronized with the network. Make sure you have peers (see the top bar) and the block number in Fusion matches the one that is shown on http://ubiqscan.io. Also check if the block number increases over time. If not, the node is not able to connect to the network. See the section "Unable to find peers".
  • If you have peers and your block number matches or differs only a couple of blocks to the one reported on http://ubiqscan.io click on the unconfirmed transaction. A popup will open which shows the transaction details and the transaction hash. The transaction hash is actually a link to ubiqscan. Click on this link. If ubiqscan shows the transaction details this means the transaction is processed and part of the blockchain, just wait before the wallet receives the block it is included. Otherwise the transaction has not been processed (yet). It is a bit harder to determine where your transaction actually is. It might have never been send onto the network.
  • In some cases Fusion can loose the connection the underlying node and therefore won't show the transaction s confirmed, please restart Fusion and see if it fixes it.

Account can't be unlocked

Please have a look at these recommendations. In some cases Fusion looses the connection the underlying node and therefore can't unlock the account. To make sure your password is correct, you can start gubiq manually using gubiq --unlock "0x123456543234565432345.." and type the password, should it unlock successfully, then you know its Fusion which lost the connection while unlocking.

I send UBQ to the wallet contract but it doesn't show up

If you send UBQ to a wallet contract, it consumes more than the minimum of 21,000 gas for a normal value transfer, as the contract will also fire logs when receiving the transaction. Make sure you send at least 50,000 gas along with your transaction.

The transaction will otherwise be reverted and the UBQ stay at its origin address.

Bind address already in use

You probably have another instance of a Ubiq node running. Firstly you may want to close it. If you don't know what is running, there are some options:

Windows

  1. Open Resources Monitor Start > All Programs > Accessories > System Tools > Resource Monitor
  2. head to Network tab, Listening ports section.
  3. Search for the program running at the 30388 port, and terminate it, possibly with help from the Task Manager.

Mac

Open Terminal app and run:

lsof -i tcp:30388

lsof -i udp:30388

Identify the PID (process ID) that's making the port 30388 busy and kill the process:

kill <NUMBER FOUND IN PREVIOUS COMMAND>. eg: kill 2121

Linux

Open your preferred console and run

netstat -vanp tcp | grep 30388

Identify the PID related to the port number and kill the process:

kill <NUMBER FOUND IN PREVIOUS COMMAND>

Add a custom footer
Add a custom sidebar
Clone this wiki locally