creating 2nd site with newt not working

[manilx]

I guess it should be possible:

I created a 2nd site using another newt instance on another server. So 2 sites connected to 2 newt's.
All seemed working until it didn't. Resources on one site stopped working or at least not working consistently.

As each newt creates one WG tunnel (to the same port), it must get confused.

So question: is this possible? If not how should 2 sites be connected?

[miloschwartz]

Hey what version of Pangolin, Gerbil, and Newt are you using?

[manilx]

Latest on all. Tag "latest"

[manilx]

The 2 newt's were on separate lan's in different locations.....
1st lan 192.168.2.0/24
2nd lan 192.168.1.0/24

[oschwartz10612]

Hum this is interesting. I was not able to reproduce. This should be supported just fine.

When you say "stopped working" what do you mean? Do you get a 404 error or a bad gateway error?

Maybe you could post the logs from both newts and Pangolin and we can take a look?

[manilx]

I just could not access the sites any longer. They didn’t open.

I think the message I got was no gateway.

I reverted all to my main single site because I needed access to the services fast.

[manilx]

After updating to beta 12. Modifying the compose.yaml to include the new network commands (didn't have any with the previous installer), I retried the 2nd newt:

Seems to be all OK now. Both sites are acessible.

Will monitor and report if something breaks.

[oschwartz10612]

Okay sounds good. We can keep this open in case there are any further issues around this.

Just one more thing: were you transferring resources at all or just creating them and eventually it stopped working?

[manilx]

I created them from scratch.

…

-- Manfred Ell

On 5. Feb 2025 at 14:06 +0000, Owen Schwartz ***@***.***>, wrote: Okay sounds good. We can keep this open in case there are any further issues around this. Just one more thing: were you transferring resources at all or just creating them and eventually it stopped working? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>