Monitoring failed for one of two same nodes
Closed this issue · 8 comments
Describe the bug
0x16687310f8dd4f1e3149e18447c5029ecb70b143 - Monitoring failed
0x4878af9ab6cb85675ec9b549565c3ef69702fc23 - works fine
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
Two nodes receive traffic well.
Screenshots
Environment (please complete the following information):
- Node version: [e.g. 1.27.0]
- OS: [e.g. ubuntu ]
- Desktop app version (if applicable): [e.g. 2.0.4]
- Docker (if applicable): specify docker version and image tag
- Your identity (if applicable): [e.g. ]
- Payment (top-op) reference (if applicable): [e.g. 1118e94e-27fc-4fd2-b604-fd26008fb709]
Additional context
Two week ago failed node goes offline and nothing can turn it back to online. rm docker run it again, reboot.
of course I've done this manual https://help.mystnodes.com/en/articles/8005254-firewall-iptables-configuration
This two nodes completly the same, same OS, Hardware, lte modem. etc..
Same here, in the NodeUI on the host, it says online. I even have a transaction. But on my nodes page, it says monitoring failed.
Ubuntu 22.04 on Raspberry Pi 4, checked iptables. UFW is set to allow 10000:60000/udp. Everything in the NodeUI seems fine.
node 1.27.0.
Some news from yesterday. The node goes online by itself. I do nothing to make it green. 🤷♂️
Maybe there are some ip checks and it was yellow by some conflict with second node... don't know and don't understand it at all.
same here, they don't seem to care, the support told me to use the one that works xD
@szferi91 I think there is some ip geo checks… there in no other explanation
@etherunit i will provide due to this bug comes again to me when my GSM LTE modem provide me same two first digits in public ip. but strange due to it has completely different sim cards.
0x4878af9ab6cb85675ec9b549565c3ef69702fc23
0x16687310f8dd4f1e3149e18447c5029ecb70b143 - monitoring failed here.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity for a long time. If this issue is still valid, please ping a maintainer and ask them to label it as "pinned". Thank you for your contributions.