Oracle has 2 very strict firewalls. You have to open ports from the oracle Web interface (mandatory) and maybe also set rules on your VM.
this post was submitted on 18 Jun 2023
14 points (93.8% liked)
Selfhosted
40727 readers
633 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Yea, its sometimes annoying when you have to manage 2 firewalls (still to this day i find the Oracle interface too messy), but it makes it secure
That was it thank you! I seen that ufw was inactive and assumed there wasn't anything else on the VM but i dug deeper and seen i needed to allow it in iptables.
You didn't say anything about firewall or security list, so did you add rules in the subnet security list of your instance and did you open ports in iptables to allow incoming traffic on NPM port?
See this blog post for more details : https://blogs.oracle.com/developers/post/enabling-network-traffic-to-ubuntu-images-in-oracle-cloud-infrastructure
None of those IPs are public so when someone external comes asking for the public IP 129.159.x.x the server will respond that it doesn't have any service running in that IP. When the service is listening to the tailscale interface and you access it through tailscale, your browser is asking the server for the content on 100.64.x.x, the tailscale IP, and so there is indeed a service on that IP. So if you want to provide a service on both the tailscale network and through the public IP, you have to use the IP 0.0.0.0 which means every interface or you can also tell nginx to listen on both the public ip and the tailscale ip. And as the other comment says, you have to allow the port connection in bot the VPS and the Oracle network, the VCN.