Temporary Tron Fullnode Issue Resolved

The Tron fullnode experienced a short-term unavailability yesterday. While it is now back online, there was a period when the fullnode returned an incorrect “last block” number before eventually providing the correct one.
If SHKeeper queried the fullnode during this period of incorrect data, it may have overwritten the “last block” number in its database with the incorrect value. As a result, SHKeeper cannot automatically update to the correct block number.
Action Required
To resolve this issue, you need to manually correct the “last block” number in the database to the value recorded before the fullnode downtime. Please execute the following commands:
kubectl -n shkeeper scale --replicas=0 deploy tron-shkeeper
sqlite3 /var/lib/rancher/k3s/storage/pvc-*_shkeeper_tron-shkeeper-data/database.db 'update settings set value=67724176 where name="last_seen_block_num"'
kubectl -n shkeeper scale --replicas=1 deploy tron-shkeeper
If you encounter any difficulties or have questions, please contact our support team for assistance.
Latest News & Announcements
-
Bitcoin Support via Public Node & Reduced Server Requirements
#announcementsWe’ve expanded SHKeeper’s capabilities!Bitcoin can now be used through a public node, without the need to run your own full node. This makes integration significantly easier and reduces setup time. In addition, thanks to support for public nodes for Bitcoin and other cryptocurrencies, the VPS requirements...
-
SHKeeper Introduces TRON Staking for Lower TRC-20 Fees
#announcementsWe have added TRON Staking to SHKeeper, including management of Energy, Bandwidth, and optional Super Representative (SR) voting.This feature helps significantly reduce TRX burn during TRC-20 payouts and makes network costs predictable. How It Works In TRON, transaction costs are paid with Bandwidth...
-
SHKeeper Update – ETH Internal Transaction Detection
#announcementsSHKeeper now automatically detects Ethereum internal transactions (transfers initiated through smart contracts, marked as Internal Transactions on Etherscan) and correctly notifies the merchant once the payment is received. Previously, such transfers were visible on-chain but were not triggering invoice...