KiraCore/kira

Issues

• Typo in seeds-edit.sh

  #519 opened a year ago by andrsj
  1

• curl dependencies that are needed for the installation script are not specified

  #499 opened 2 years ago by PeepoFrog
  1

• Locked interaction with containers after rebooting

  #504 opened 2 years ago by andrsj
  0

• Backup chain state failing in loop

  #343 opened 3 years ago by dragonstake
  1

• v0.4.0.5 validator goes over to inactive mode (VALIDATOR WAS STOPED, PLEASE ACTIVATE YOUR NODE)

  #263 opened 3 years ago by goganaut
  1

• whitelisted but still All ports are open to public message

  #260 opened 3 years ago by Creamers158
  2

• apt auto remove confirmation question

  #258 opened 3 years ago by Creamers158
  1

• change infrastructure exits setup

  #257 opened 3 years ago by Creamers158
  1

• INFRASTRUCTURE IS UNHEALTHY

  #241 opened 3 years ago by 8888-droid
  1

• Menu items shifted

  #259 opened 3 years ago by Creamers158
  1

• ISSUES DETECTED

  #264 opened 3 years ago by NormanBB
  0

• Nodes stuck in testnet-3

  #256 opened 3 years ago by dhinio52
  0

• sentry container does not exists yet

  #230 opened 3 years ago by Creamers158
  1

• A Small Suggestion

  #227 opened 3 years ago by NormanBB
  1

• latest setup asking confirmation

  #226 opened 3 years ago by Creamers158
  2

• Your node setup FAILED

  #219 opened 4 years ago by DenysOf
  1

• discovery/updating of public_ip and local_ip fails

  #218 opened 4 years ago by Creamers158
  1

• kiramanager not fully working / halting

  #217 opened 4 years ago by Creamers158
  1

• Seed nodes failed while updating KIRA

  #176 opened 4 years ago by sprprashanth1443
  1

• minimal block before signing give negative value

  #173 opened 4 years ago by Creamers158
  2

• Run Kira's unrelated container makes validator INACTIVE

  #166 opened 4 years ago by ilfroloff
  2

• priv_sentry node stuck to restart

  #130 opened 4 years ago by phamhung3589
  2

• Validator stuck in starting loop

  #110 opened 4 years ago by valNodeOne
  1

• Bug - Manage validator : exited

  #111 opened 4 years ago by jonhh12
  1

• Latest Patch for testnet-2 bring a lot of validator nodes to INACTIVE status

  #112 opened 4 years ago by exidz
  1

• Error message exit Edit/Show SEED Nodes List

  #146 opened 4 years ago by valNodeOne
  1

• Installing without supplying / saving public peer

  #149 opened 4 years ago by Creamers158
  3

• Temporary failure in name resolution || Can't docker push the repository (base image) in some VPS provider (e.g. contabo)

  #75 opened 4 years ago by exidz
  4

• Catching up status turns False after joining a network

  #45 opened 4 years ago by alkadeta
  3

• Consensus stopped height 9901

  #94 opened 4 years ago by valNodeOne
  1

• Most of the docker containers show unhealthy status

  #77 opened 4 years ago by DenysOf
  1

• ISSUES DETECTED, INFRASTRUCTURE IS UNHEALTHY

  #78 opened 4 years ago by giahung24
  1

• Snapshot monitoring high CPU consumption

  #81 opened 4 years ago by bsrinivas8687
  1

• Never received 'waiting' status and infrastructure is unhealthy

  #93 opened 4 years ago by danenright
  1

• Container blocks stuck at 49999 since 09.52 (UTC+0)

  #79 opened 4 years ago by alkadeta
  2

• Infrastructure is unhealthy and stuck at block 49999

  #80 opened 4 years ago by liray-unendlich
  1

• High disk consumption

  #95 opened 4 years ago by derfredy
  1

• Private and Public sentries are named incorrectly

  #76 opened 4 years ago by derfredy
  3

• Installation | Recurring NetworkManager.service not found | Could lead to incorrect interpretation

  #68 opened 4 years ago by WayneWayner
  2

• Can not restart containers after a [S] STOP All Containers

  #40 opened 4 years ago by derfredy
  2

• DynDNS can not be passed to [J]oin networks

  #41 opened 4 years ago by derfredy
  1

• nginx service not starting on frontend container

  #38 opened 4 years ago by derfredy
  9

• Address '1**.***.***.**2' is not a valid, publicly exposed public node address

  #39 opened 4 years ago by alkadeta
  2

• Error: No pubspec.yaml file found.

  #33 opened 4 years ago by HankFit247
  1

• Problem: ERROR: Failed to launch the infrastructure

  #32 opened 4 years ago by HankFit247
  1

• Deployment tool | /etc/default/apport' does NOT exist

  #9 opened 4 years ago by WayneWayner
  1