quietsy/Securing-SWAG.md

Last active October 8, 2024 11:00

Star () You must be signed in to star a gist
Fork () You must be signed in to fork a gist

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/quietsy/58590a640dd4f7a89696c68b0e6a8691.js"></script>
Save quietsy/58590a640dd4f7a89696c68b0e6a8691 to your computer and use it in GitHub Desktop.

Download ZIP

Securing SWAG

Raw

Securing-SWAG.md

Moved to https://virtualize.link/secure/

behnam-io commented Dec 6, 2021 •

edited

Loading

@drizuid thanks for the guide. I turned it on, but it doesn't hide my server's IP. I ping my docker image's domain and I get my server's IP.

UPDATE:
I tested your mod. But didn't understand what it does, precisely (for my case).

I think i'm getting close to some clues. Found this on cloudflare's website:

Yes. Cloudflare supports the wildcard '*' record for DNS management in all customer plans.
Free, Pro, and Business plans
Non-enterprise customers can create but not proxy wildcard records.

I had used wildcard CNAME record. that's why my subdomain was getting exposed.

Now, idealistically I want something to overcome this issue, cause I have more than handful of sudbomains, but otherwise it's still possible to hide my server's IP by adding A records in CF manually.

agingorange commented Jan 10, 2022

That was a good read, @quietsy. I'm using lscr.io/linuxserver/swag and I want to do geo blocking, but there is no geoip2.conf and no mention of it in nginx.conf? Should I look for another image?

Author

quietsy commented Jan 10, 2022

Hey @agingorange , please use the updated guide at https://virtualize.link/secure/

agingorange commented Jan 10, 2022

@quietsy Fantastic. Thanks much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment