Jump to content

I get error Transaction is not validated yet and eventually transaction fails and is not registered on ledger?


Recommended Posts

Hi, I installed rippled node running inside a container. Everything works fine apart from transaction, it just gets submitted and i get tesSuccess but is never validated. 

I have enabled history sharding with 50 gb and node size set to medium

right now the docker image has only occuppied like 6.7 gb, I am inferring that this problem might be because it does not has complete history or is missing shards and transaction will only be validated properly after 50gb is downloaded

or i dont know if i am doing something wrong here, below is my config - i am using https://github.com/WietseWind/docker-rippled/blob/master/Dockerfile this docker image and have edited the config file as below. Thanks in advance.

#  https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg
#       To accept connections on well known ports such as 80 (HTTP) or
#       443 (HTTPS), most operating systems will require rippled to
#       run with administrator privileges, or else rippled will not start.

#ssl_key = /etc/ssl/private/server.key
#ssl_cert = /etc/ssl/certs/server.crt

port = 5005
ip =
admin =
protocol = http

port = 51235
ip =
# alternatively, to accept connections on IPv4 + IPv6, use:
#ip = ::
protocol = peer

port = 80
ip =
protocol = ws

port = 6006
ip =
admin =
protocol = ws



# This is the persistent datastore for shards. It is important for the health
# of the ripple network that rippled operators shard as much as practical.
# NuDB requires SSD storage. Helpful information can be found at
# https://xrpl.org/history-sharding.html


# This needs to be an absolute directory reference, not a relative one.
# Modify this value as required.


# To use the XRP test network
# (see https://xrpl.org/connect-your-rippled-to-the-xrp-test-net.html),
# use the following [ips] section:
r.altnet.rippletest.net 51235

# File containing trusted validator keys or validator list publishers.
# Unless an absolute path is specified, it will be considered relative to the
# folder in which the rippled.cfg file is located.

# Turn down default logging to save disk space in the long run.
# Valid values here are trace, debug, info, warning, error, and fatal
{ "command": "log_level", "severity": "warning" }

# If ssl_verify is 1, certificates will be validated.
# To allow the use of self-signed certificates for development or internal use,
# set to ssl_verify to 0.



Link to comment
Share on other sites

  • Replies 1
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...