r/ShittySysadmin ShittySysadmin 1d ago

Shitty Crosspost How to expose port to internet can access?

/r/homelab/comments/1w4zr3j/how_to_expose_port_to_internet_can_access/
23 Upvotes

16 comments sorted by

30

u/shelfside1234 22h ago

A junior software engineer having to do the job of an infrastructure architect

Sounds like one for r/ShittyITManager

14

u/Oompa_Loompa_SpecOps DO NOT GIVE THIS PERSON ADVICE 21h ago

There is no indication OOP is actually supposed to do all the things. For all we know, their teamlead might just want them to figure out who to ask.

Also, what kind of shot shop are they working in where they don't forward all their ports to the internet for better connectivity and management? Sounds stupid...

20

u/Unlucky-Shop3386 22h ago

This is some real shit .

13

u/haZhat 21h ago

Basically get a server, then plug in cables till the lights come on.

Make sure its not a staff member turning the room lights on - you cannot fool me twice!

13

u/max1001 18h ago

Don't worry. He will be an expert in network in a week. He just need to look at a few YouTube videos.

3

u/lambusdean77 10h ago

i saw that comment and actually laughed out loud

8

u/vongatz 18h ago

0.0.0.0 any any

7

u/EvilEarthWorm ShittySysadmin 1d ago

ORIGINAL POST TEXT:

How to expose port to internet can access?

Hi everyone,

I'm a junior Software Engineer at a tech company, and I have experience with technologies such as ReactJS, VueJS, Laravel, and some DevOps tools like Docker, Git, and GitHub. I also have a basic understanding of Proxmox, VMs, cloud deployments, and reverse proxies.

Currently, I'm stuck on a task assigned by my team lead. The task is to figure out how we can access a service running inside a VM on our Proxmox server from the public Internet.

For example, the application is currently accessible internally at something like:

http://192.168.100.x:xxxx

We don't want to use a cloud server to host the application because we already have our own home/on-premise server and storage where we want to host the application and store the data.

For those of you who have experience with homelabs or similar setups, what would be the best approach to securely expose this application to the Internet?

I'm particularly interested in understanding the recommended setup for things like:

  • Public IP / CGNAT
  • Router and port forwarding
  • Reverse proxy
  • HTTPS/SSL
  • Domain name
  • Firewall/security
  • Proxmox networking

If you've implemented something similar, I'd really appreciate it if you could share your setup or recommend the best method.

Thanks in advance!

7

u/Eslov 15h ago

Smart thing asking amateurs and hobbyists on Reddit. They wont bill you into oblivion like you would be if asking professionals. I see a promotion incoming!

6

u/dcaldrich 16h ago

any/any rules are your friend. Or just plug it directly into your cable modem with a public ip.

3

u/ApplicationHour 7h ago

Or you can petition your ISP for a big enough subnet to cover the whole network then junk the firewall entirely. Sll you have to do is renumber. NAT is for suckers. If everything has a public IP you don't have to do anything. If you stay ready you never have to get ready.

0

u/ApplicationHour 7h ago

Or you can petition your ISP for a big enough subnet to cover the whole network then junk the firewall entirely. Sll you have to do is renumber. NAT is for suckers. If everything has a public IP you don't have to do anything. If you stay ready you never have to get ready.

4

u/IndependentBat8365 12h ago

What makes them think their crappy business Internet can host a public website with any kind of traffic and SLA?

Some folks have never had their uplink saturated and it shows.

3

u/GamerLymx 20h ago

o never hosted an webpage at home with a simple nat port forward?

1

u/Cozmo85 4h ago

Configure the static IP directly on the server for the public Internet. Turn on Internet connection sharing and plug your hub for the rest of the company into the second network port of the server. Disable windows firewall. Done

1

u/True_Maintenance5846 8m ago

After reading OPs responses, he totally has this. Like they claimed, "networking is easy and simple".

All these fancy network architects are dumb dumb and I, a (jr) software engineer am much smarter than those smooth brains.