search

NOXCIS / Wiregate

"WireGate: Secure Intranet Deployment with WireGuard, Docker, and Enhanced Network Controls"
MIT License
207 stars 4 forks source link

Automatic server ip detection not working #36

Closed Kapyyyy closed 7 months ago

Kapyyyy commented 7 months ago

I'm running this on an oracle vps on ubuntu 20.04 Lts and I encountered this issue before while using worm-hole as well, but back then the installer let me set the server ip manually which helped me get it working.

I ran the installer script in both deploy modes, but neither figured out the ip correctly and neither let me set it manually.

NOXCIS commented 7 months ago

Not sure why server ip detection isn't working for you, but the wiregate container environment can be preconfigured for your use case check dev-docker-compose for reference.

NOXCIS commented 7 months ago

You can find the origin compose files in Global Configs

NOXCIS commented 7 months ago

Or use the preconfigured option and fillout the wiregate.env in global configs

Kapyyyy commented 7 months ago

It seems to be grabbing the internal ip instead of the external one.

8beet commented 7 months ago

You can also manually configure the peer remote endpoint after setup in the Dashboard.

go to settings > peer remote endpoint and enter your public IP - then download fresh QR or .conf files

8beet commented 7 months ago

@NOXCIS i do have the same issue where it auto detects my local IP for the wiregate server but I this fix works easily enough.

NOXCIS commented 7 months ago

Ill re-add the manual set for server IP in the Kraken release comming in a few days

NOXCIS commented 7 months ago

All the installer really does is allow you to deploy without hardcoded environment variables in the compose.