Newt pulled Resources for another Site #1833

New Issue

MrUnknownDE · 2026-04-05T19:42:33+02:00

MrUnknownDE commented

2026-04-05 19:42:33 +02:00

Originally created by @nixielectra on 1/31/2025

Hi,

I have installed two Newts in two different server, melaka and banting. When I started the Newt in banting it pulled Resources which were configured for melaka. I didn't remember seeing this in previous version.

Pangolin version: beta.9
Newt version: beta.5

Sites

Resources

Newt melaka (Expected behavior)

INFO: 2025/01/31 01:01:57 Not adding target because not running
INFO: 2025/01/31 01:01:57 Not adding target because not running
INFO: 2025/01/31 01:01:57 Not adding target because not running
INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:61907 to pihole:80
INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:57631 to wgeasydns:xx
INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:47178 to wgeasyfull:xx

Newt banting (Wrong behavior?)

INFO: 2025/01/31 00:40:16 Starting ping check
INFO: 2025/01/31 00:40:16 Not adding target because not running
INFO: 2025/01/31 00:40:16 Not adding target because not running
INFO: 2025/01/31 00:40:16 Not adding target because not running
INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:61907 to pihole:80
INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:57631 to wgeasydns:xx
INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:47178 to wgeasyfull:xx

*Originally created by @nixielectra on 1/31/2025* Hi, I have installed two Newts in two different server, `melaka` and `banting`. When I started the Newt in `banting` it pulled Resources which were configured for `melaka`. I didn't remember seeing this in previous version. Pangolin version: `beta.9` Newt version: `beta.5` Sites ![Image](https://github.com/user-attachments/assets/5cf53df7-8bb9-4c6c-a431-26b1ce07f274) Resources ![Image](https://github.com/user-attachments/assets/7b6759ff-56cd-4687-b079-3b35deda0e16) Newt `melaka` (Expected behavior) ``` INFO: 2025/01/31 01:01:57 Not adding target because not running INFO: 2025/01/31 01:01:57 Not adding target because not running INFO: 2025/01/31 01:01:57 Not adding target because not running INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:61907 to pihole:80 INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:57631 to wgeasydns:xx INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:47178 to wgeasyfull:xx ``` Newt `banting` (Wrong behavior?) ``` INFO: 2025/01/31 00:40:16 Starting ping check INFO: 2025/01/31 00:40:16 Not adding target because not running INFO: 2025/01/31 00:40:16 Not adding target because not running INFO: 2025/01/31 00:40:16 Not adding target because not running INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:61907 to pihole:80 INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:57631 to wgeasydns:xx INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:47178 to wgeasyfull:xx ```

MrUnknownDE closed this issue

2026-04-05 19:42:33 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#1833