Vultr doesn't work

[hrdwdmrbl]

Describe the bug

Background

I have set up working Outline servers with Digital Ocean, AWS vanilla, AWS Lightsail and Google Cloud. I wanted to try Vultr because of their great price. I had tried it a little while ago to get it to work and then tried again today.

Bug

The problem is that all the setup and even connecting works, but then I can't connect to anything after connecting to my Outline server. I cannot SSH my instance or load any website such as example.com I am able to do a traceroute to my Vultr instance (14 steps), but not to any domain like example.com I cannot ping domains either, like example.com I can curl example.com from Vultr when not connected to it using Outline so I know that the instance has internet.

To Reproduce Steps to reproduce the behavior:

1. Create instance on Vultr
2. Install Outline software
3. Set up firewall for TCP and UDP 1024-65535
4. Copy key from Manager to Client
5. Connect to server
6. No connection :(

Expected behavior Should connect

Screenshots Would prefer not

Desktop (please complete the following information):

• OS: Ubuntu 18.04 and 18.10
• Browser Firefox, iTerm, etc
• Outline Client Version 1.2.5

[hrdwdmrbl]

Anyone get it working on Vultr? If so, is there a normal step that I'm forgetting or missing?

[nonewind]

If your ssh can't connect, can you consider GFW?Or change a server?

[hrdwdmrbl]

I can SSH while not connected with Outline. I have also tried setting up multiple Vultr instances but all had the same problem. It could be GFW but it's only happening with Vultr...

[nonewind]

I also encountered on BanwagonHost CN2 server unable to SSH, but can ping. Probably only in IP can be solved. You can see that ！=> https://www.daehub.com/archives/8933.html May explain your problem.

[hrdwdmrbl]

@Zhangziheng1 I was not even able to ping it at any time. (in the comments of that blog post you sent someone posted a link to a hosted SS service that I signed up for though :) )

[ghost]

Several people have reported Vultr and Bandwagon are quickly walled.

[hrdwdmrbl]

@lwyh It seems to be instant though which makes me suspect that the problem isn't that it's being walled. I do not know much about walling system though, so for all I know they could be able to block traffic as soon as they see the establishment of a connection. If it is being walled, my question would be about what makes Vultr and Bandwagon different?

[ghost]

We can only speculate. Vultr and Bandwagon are very popular. It is possible that the previous owner of the VPS used it for a Shadowsocks server, it got detected, and the IP address was blocked even before you bought it. There are some suggestions for VPS location in Chinese here https://doubibackup.com/hi10k-7p-3.html and here https://doubibackup.com/wkcjzpyd-2.html summarized in English in section “1. VPS location” here https://medium.com/@phoebecross/bypass-gfw-china-2019-dc5959658c3b

[kakajansh]

I have same issue with Vultr

[louis-eyond]

I'm also seeing issue with Vultr, initial connection is good for about 5 minutes, then all Internet traffic is blocked.

[sysk]

Same issue here (I tested Singapore VPS). When i do manage to connect to the server (it happens after trying several times), I can't connect to anything.

[LBYPatrick]

You might want to try the old-school shadowsocks-libev on the server end and a traditional shadowsocks client (shadowsocks-windows, shadowsocks-qt5, etc.) and see what happens. If it still doesn't connect, then I would suggest you to change your server IP.

For Vultr, you might want to avoid server IPs that starts with 45. because GFW has banned the majority of them.

If you want to do quick shadowsocks server deployment, try this software. The "SS Link" generated by info feature works PERFECTLY with Outline and any standard shadowsocks software.

[DeanStern]

I also encourage this issue in Vultr, what are the servers hosting you managed to get work with SS?

[silvere]

Same problem...

[commanderinchief]

Try with following command in your console. sudo ufw allow [remote port no] sudo ufw allow [client port no]

[LBYPatrick]

It's 2021 and the issue is still open...

I recently encountered the same issue and found out that net.ipv4.ip_forward is commented out in /etc/sysctl.conf, which was not the case when I set up my Vultr VPS back in 2017.

To resolve this, simply add the following line to /etc/syctl.conf

net.ipv4.ip_forward = 1

and either reboot your Vultr machine or run the following command in bash as root:

sysctl --system

Problem solved.

[talyguryn]

Due to security policies Vultr blocks every other connections except to 22 port by default.

You can check available ports after internal firewall. mine was:

root@vultr:~# ufw status
Status: active

To                         Action      From
--                         ------      ----
22                         ALLOW       Anywhere                  
22 (v6)                    ALLOW       Anywhere (v6)             

Then you need to open two more for the outline managing and connection (22222 and 44444 for example):

root@vultr:~# ufw allow 22222
Rule added
Rule added (v6)

root@vultr:~# ufw allow 44444
Rule added
Rule added (v6)

That's it! Now you will be able to connect.

How I ran Outline VPN on Vultr // codex.so

[ashki23]

This worked for me:

sudo ufw allow <management_port>/tcp
sudo ufw allow <key_port>/tcp
sudo ufw allow <key_port>/udp

When the Outline setup is completed, it shows the parts that need to be opened. The Key Port number is the same as the "Port for new access keys" in your Outline Server settings.