Replies: 1 comment
-
I'm not sure you should be redirecting to it. H-ui sets up proxying the site content from the other URL, for example. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I'm a new XRay user from Russia and quite a noob at all this networking stuff. Although I've been diligently reading up on all sorts of tutorials and posts here, there are some walls I can't overcome on my own. So I've set up an xray service on a VPS and set-up clients on my devices. It works so far. But I'm concerned about the future possibility of my VPS being flagged as a VPN/proxy and being blocked, and wanted to know your advice on proper security measures to avoid this as much as possible. I can see that there are a lot of example configs but I can't figure out how they're different and which one is better and how it needs to be implemented. I'm seeing that everybody's talking about XHTTP3 as being the best for security in the long run, but there're no info regarding implementation and pre-requisites. Any place I can read up on that?
What security measures am I talking about? For example when I input my VPS's IP in the browser I should be redirected to the web-site that I'm pretending to be with xray. Otherwise masking doesn't work, right? But I only managed to do so for HTTP on port 80, but when I try to enter https://IP:443 it gives me an error (ERR_HTTP2_PROTOCOL_ERROR).
Here's a summary of my current configurations:
NAT Table:
Filter Table:
Here are raw configs (with sensitive info censored):
Xray Configuration (/usr/local/etc/xray/config.json):
Nginx Configuration (/etc/nginx/sites-enabled/redirect):
Current IPTables Rules:
NAT Table (empty)
Filter Table:
I've changed the real domain name and IP address of the site I'm pretending to be.
Beta Was this translation helpful? Give feedback.
All reactions