Can't access instance via public IP after successful install

[orhanmaden]

Describe the bug
Can't access instance via public IP after successful install

To Reproduce
Steps to reproduce the behavior:

1. Create a Digital Ocean droplet with a Debian 10 x64 instance with 4 GB / 2 CPUs, 80 GB SSD Disk and 4 TB transfer
2. Install curl: sudo apt install curl -y
3. Download script: curl -s https://api.github.com/repos/tmiland/Invidious-Updater/releases/latest | grep "browser_download_url.*sh" | cut -d : -f 2,3 | tr -d \" | wget -qi -
4. Set permissions: chmod +x invidious_update.sh
5. Run script: ./invidious_update.sh
6. Set advanced options:
   
7. Let the script run to success:
   

Expected behavior
Instance is accessible via the IP address. Unfortunately that is not the case:

Screenshots
Added above

Desktop (please complete the following information):

• OS: Debian 10 x64
• Browser: Chrome v88.0.4324.190

Additional info
The instance is removed to prevent costs

[tmiland]

Hello,

seems like port 80 is blocked in your firewall.

[orhanmaden]

Thanks for the quick response. I did the following to tackle the potential issue.

Installed ufw: apt install ufw -y
Enabled it: ufw enable
Allowed traffic through port 80: ufw allow http
Checked status: ufw status verbose
Output:

Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip

To                         Action      From
--                         ------      ----
80/tcp                     ALLOW IN    Anywhere
80/tcp (v6)                ALLOW IN    Anywhere (v6)

It it still not accessible from the public IP. Am I missing something?

[tmiland]

I haven't tested a setup like this, so i cannot tell unfortunately.

However, you could set it up to run like this:

✔ branch        : master
✔ domain        : invidious.tube
✔ ip address    : your_droplet_public_ip
✔ port          : 3000
✔ external port : 443
✔ dbname        : invidious
✔ dbpass        : secretpassword
✔ https only    : true

Then use option 9 to setup Nginx. Just go through step 1-3.

It will then serve invidious from port 3000 reverse proxied to port 443 (https) 👍

Make sure port 443 is open in your firewall.

This is how it's expected to be run on a public IP.

[orhanmaden]

I tried your suggestion and that didn't work. After fiddling for a day I got it working with the following configuration

And than the channels gave an error. I give up for now

[tmiland]

Sorry to hear it didn't work out.

The channel error is a bug with invidious: iv-org/invidious#1838