[DiscordArchive] Is your server generally available to the internet/anyone? Or is it just intended for internal usage
[DiscordArchive] Is your server generally available to the internet/anyone? Or is it just intended for internal usage
Original source
Is your server generally available to the internet/anyone? Or is it just intended for internal usage?
rektbyfaith
10-20-2023, 04:18 PM #1Archived author: Abillister • Posted: 2023-10-20T16:18:43.459000+00:00
Original source
Is your server generally available to the internet/anyone? Or is it just intended for internal usage?
Original source
How do I fix the game resolution to 1920×1080
rektbyfaith
10-20-2023, 04:20 PM #2Archived author: Deleted User • Posted: 2023-10-20T16:20:10.149000+00:00
Original source
How do I fix the game resolution to 1920×1080
Original source
I have it on my vps
rektbyfaith
10-20-2023, 04:21 PM #3Archived author: Charles Collins • Posted: 2023-10-20T16:21:25.298000+00:00
Original source
I have it on my vps
Original source
Sure but that doesn't answer who should have access to it. If you are getting direct IP hits from internet IP's that would indicate that your server/port is exposed to the internet.
rektbyfaith
10-20-2023, 04:23 PM #4Archived author: Abillister • Posted: 2023-10-20T16:23:17.256000+00:00
Original source
Sure but that doesn't answer who should have access to it. If you are getting direct IP hits from internet IP's that would indicate that your server/port is exposed to the internet.
Original source
Stopping people you don't want from accessing it would come down more to firewall settings.
rektbyfaith
10-20-2023, 04:23 PM #5Archived author: Abillister • Posted: 2023-10-20T16:23:51.135000+00:00
Original source
Stopping people you don't want from accessing it would come down more to firewall settings.
Original source
I use Ufw on debian I put each of these addresses in a block I just don't know if it's enough
rektbyfaith
10-20-2023, 04:26 PM #6Archived author: Charles Collins • Posted: 2023-10-20T16:26:24.143000+00:00
Original source
I use Ufw on debian I put each of these addresses in a block I just don't know if it's enough
Original source
Well theoreticlly it should block them but it would mean you need to continually keep manually adding these as they come up.
rektbyfaith
10-20-2023, 04:27 PM #7Archived author: Abillister • Posted: 2023-10-20T16:27:18.798000+00:00
Original source
Well theoreticlly it should block them but it would mean you need to continually keep manually adding these as they come up.
Original source
So either you would need to add a script in or come up with a different method of connecting. Since my server is just used by myself and some close friends/family I just setup a simple L2TP/IPSEC VPN - I used L2TP because the built in windows VPN can handle it and i wanted to keep the instructions simple (for example my mother plays who is not very computer savvy).
rektbyfaith
10-20-2023, 04:28 PM #8Archived author: Abillister • Posted: 2023-10-20T16:28:25.309000+00:00
Original source
So either you would need to add a script in or come up with a different method of connecting. Since my server is just used by myself and some close friends/family I just setup a simple L2TP/IPSEC VPN - I used L2TP because the built in windows VPN can handle it and i wanted to keep the instructions simple (for example my mother plays who is not very computer savvy).
Original source
So the only exposed ports is for the VPN service, which then has a fairly strong double password (first on pre-shared key, the on the user...though the firewall I'm using doesn't natively support multiple users per tunnel so I just have 1 user. It is more intended for site-to-site vs "road warriors"). That way any intrusion is just hitting the firewall and needs to defeat the VPN login before gaining access to the actual server behind it.
But that works for me since I have a limited target audience access it.
rektbyfaith
10-20-2023, 04:29 PM #9Archived author: Abillister • Posted: 2023-10-20T16:29:58.878000+00:00
Original source
So the only exposed ports is for the VPN service, which then has a fairly strong double password (first on pre-shared key, the on the user...though the firewall I'm using doesn't natively support multiple users per tunnel so I just have 1 user. It is more intended for site-to-site vs "road warriors"). That way any intrusion is just hitting the firewall and needs to defeat the VPN login before gaining access to the actual server behind it.
But that works for me since I have a limited target audience access it.
Original source
If your users are "region" specific you could also use a Geo IP blocking concept - but rather than complicating it with block lists you could just put YOUR region as the only allowed IP ranges. It won't 100% prevent it but will greatly reduce it.
rektbyfaith
10-20-2023, 04:31 PM #10Archived author: Abillister • Posted: 2023-10-20T16:31:53.904000+00:00
Original source
If your users are "region" specific you could also use a Geo IP blocking concept - but rather than complicating it with block lists you could just put YOUR region as the only allowed IP ranges. It won't 100% prevent it but will greatly reduce it.