fixed unsynced index.html

This commit is contained in:
Zer0 2024-11-24 17:06:29 +01:00
parent d2eaec69b8
commit f36ae94d51

View file

@ -142,6 +142,31 @@
</blockquote>
<br><br>
</li>
<li id="clients">
<h3><u> Clients</u></h3>
<span>Android
<ul>
<li><a href="httphttps://github.com/MatsuriDayo/NekoBoxForAndroid/">Nekobox</a></li>
<li><a href="https://github.com/2dust/v2rayNG">v2rayNG</a></li>
</ul>
</span>
<span>Linux
<ul>
<li><a href="https://github.com/Matsuridayo/nekoray">Nekoray</a></li>
<li><a href="https://github.com/2dust/v2rayN">v2rayN</a></li>
<li><a href="https://github.com/v2rayA/v2rayA">v2rayA</a></li>
<li><a href="https://github.com/LorenEteval/Furious">Furious</a></li>
</ul>
</span>
<span>Windows
<ul>
<li><a href="https://github.com/hiddify/HiddifyN">HiddifyN</a></li>
<li><a href="https://github.com/2dust/v2rayN">v2rayN</a></li>
</ul>
</span>
<p>
</p>
</li>
</ul>
</p>
</div>
@ -172,17 +197,174 @@
<p>Looking kinda complicated right, fear not we have Web-UI's to setup V2Ray servers.
<mark>Web-UI aka "panels" </mark>could be used for user-management including traffic stats,uuid-generation and much more...
</p>
<img src="" class="imgRz">
<pre><code class="nim">
</code></pre>
<p></p>
<img src="" class="imgRz">
<pre><code class="nim">
</code></pre>
</code>
</pre>
<ul>
<li>
<h3><u>Getting a VPS</u></h3>
<p>
refer to <a href="https://blog.nowhere.moe/opsec/anonymousremoteserver/index.html">Acquiring remote servers anonymously (non-KYC providers) </a>
for buying a <b>VPS using XMR</b>
</p>
<br><br>
</li>
<li>
<h3><u>Installing a panel</u></h3>
<p>Once you have the VPS ready and have established an SSH connection,we can start working on installing panel.</p>
<blockquote class="blockquote">
we'll be using <b><a href="https://github.com/alireza0/x-ui">alireza0/x-ui</a></b> panel since its actively
maintained, you could also use <b><a href="https://github.com/MHSanaei/3x-ui">MHSanaei/3x-ui</a></b>
.The v2ray server setup is same same for all.
</blockquote>
<p class="lead" style="white-space: pre-line">
Supported distributions
- Ubuntu 20.04+
- Debian 11+
- CentOS 8+
- OpenEuler 22.03+
- Fedora 36+
- Arch Linux
- Parch Linux
- Manjaro
- Armbian
- AlmaLinux 8.0+
- Rocky Linux 8+
- Oracle Linux 8+
- OpenSUSE Tumbleweed
- Amazon Linux 2023</p>
<p>
<pre>
<code class="nim">
#> bash <(curl -Ls https://raw.githubusercontent.com/alireza0/x-ui/master/install.sh)
....
Would you like to customize the Panel Port settings? (If not, random port will be applied) [y/n]: y
Please set up the panel port: 9566
Your Panel Port is: 9566
Port set successfully: 9566
Username and password updated successfully
Base URI path set successfully
This is a fresh installation, generating random login info for security concerns:
###############################################
Username: fU8hjnoLSp
Password: ak8jX44rZy
Port: 9566
WebBasePath: EwAJmwAHwMk7FLK
###############################################
If you forgot your login info, you can type 'x-ui settings' to check
Start migrating database...
Migration done!
Created symlink '/etc/systemd/system/multi-user.target.wants/x-ui.service' → '/etc/systemd/system/x-ui.service'.
x-ui v1.8.7 installation finished, it is up and running now...
</code> </pre>
The script asks for the port to use. we could change the port later.
We could use the creds(Autogenerated) displayed above to access the webui
<pre><code class="nim">X-UI Control Menu Usage
------------------------------------------
SUBCOMMANDS:
x-ui - Admin Management Script
x-ui start - Start
x-ui stop - Stop
x-ui restart - Restart
x-ui status - Current Status
x-ui settings - Current Settings
x-ui enable - Enable Autostart on OS Startup
x-ui disable - Disable Autostart on OS Startup
x-ui log - Check Logs
x-ui update - Update
x-ui install - Install
x-ui uninstall - Uninstall
x-ui help - Control Menu Usage
------------------------------------------
</code></pre>
In order to access the web UI, the url schema looks like this.
<br>
<code>http://server_ip:port/path</code>
<br><br>
<blockquote class="blockquote">
You can use <b>x-ui settings</b> command to retrieve panel info, like port and path.
<br>
Ex-output:
<br>
###############################################
Username: fU8hjnoLSp <br>
Password: ak8jX44rZy <br>
Port: 9566 <br>
WebBasePath: EwAJmwAHwMk7FLK <br>
###############################################
</blockquote>
<p class="lead" class="nim">Example
http://127.0.0.1:9566/EwAJmwAHwMk7FLK/
<br>Once you access the web portal,use the username and password as above.
</p>
</p>
<br><br>
</li>
<li>
<h3><u>Setting up the panel</u></h3>
<div style="display: flex;flex-direction: column;">
<img src="./login.png" width="50%" srcset="">
<h5>
after logging in switch to latest the xray-core
</h5>
<img src="./changexcore.png" width="100%" srcset="">
</div>
<p>In order to receive inbounds we must create an inbound rule within the panel.
<br>
We are choosing vmess (as protocol) + websocket (as trasport).
copy the settings as below.
<br>
(you could change the port as of your liking)
<blockquote class="blockquote">
VLESS does not provide built-in encryption, avoiding it for now.
<a href="https://xtls.github.io/en/config/inbounds/vless.html#vless">ref</a>
NOTE: VMess Requires to have time synced up.
</blockquote>
<img src="./createib.png" width="100%">
<br>
Now you could try to connect to the server using QR Code or by using the vmess link.
<br>
(Click the QR to copy link)
See <a href="#clients">Client Section</a>
<br><br>
<blockquote class="blockquote">
a vmess link will look like vmess://&ltuuid&gt@&lthostname&gt:&ltport&gt?&ltother_params&gt#&ltremarks&gt
</blockquote>
</p>
</li>
<li>
<h3><u>Client Installation
</u></h3>
</li>
We're installing <b>V2rayN</b> on linux, one could find the pre-build binaries in the releases section on github( <a href="https://github.com/2dust/v2rayN/releases">link</a> )
<img src="./v2rayn_release.png" alt="" srcset="">
<br>
Extract, and run the client as follows
<br>
<pre>
<code>
$ unzip v2rayN-linux-64.zip
...
$ cd v2rayN-linux-64/
$ chmod +x v2rayN
$ ./v2rayN
</code>
</pre>
<br>
change route settings (optional)
<br>
<br>
<img src="./russia.png" alt="">
<br>
<br>
Thats it !
</ul>
</div>
</div><!-- /row -->
</div> <!-- /container -->
@ -190,31 +372,149 @@
<!-- +++++ Second Post +++++ -->
<div id="anon1">
<div id="anon3">
<div class="container">
<div class="row">
<div class="col-lg-8 col-lg-offset-2">
<h2><b>Using Cloudflare Workers</b></h2> </br> </br>
<p></p>
<pre><code class="nim">
</code></pre>
<h2><b>Configuration</b></h2>
<br><br>
<p>
Setting up a v2ray server alone doesnt bypass any censors(it would be obvious if we push a large amount of traffic),rather we use some methods to make the traffic look geniune.
<br>One such method is called <b>Domain Fronting</b>
<br>
<img src="./domainfronting_diagram.png" width="100%">
<br><br>
We will be using Fastly, since it offers a free CDN without CreditCard + 30-day Websocket support(free-trial)
<br>
Start by creating an account at <a href="http://fastly.com">Fastly</a>
<br>
<img src="./fastly_newacc.png" width="50%">
<br>
Create a new cdn service like this
<br>
<img src="./cdn_newservice.png" width="50%">
<blockquote class="blockquote">
In here we can <b>use any domain name</b> since its for internal routing within cdn.
<br>
(meaning that within the CDN domain zero-google.com will resolve to our v2ray IP )
<br>
<b>origin</b> willbe our v2ray inbound IP
</blockquote>
<br>
then select the cdn name to edit the config
<br>
<img src="./cdn_edit.png" width="80%">
<br><br>
We edit the CDN config to change the port of our host and disable some settings that may cause issues
<br>
<img src="./cdn_host_change.png" width="100%">
<br>
After that we change the port from 443 to 53254 (The port we used for receiving inbounds in our v2ray panel)
<img src="./cdn_host_tls_port.png" width="100%">
<br><br>
<blockquote class="blockquote">
We can do inbounds to port 443(TLS port) and adjust inbound settings to have <b>Fallback</b> but that requires one to have an inbound config with TCP transport within the panel.
<p></p>
<pre><code class="nim">
</code></pre>
<p></p>
<pre><code class="nim">
</code></pre>
</blockquote>
TODO: Explain fallback above somewhere or here
<br><br>
Now from Settings >>
<img src="./cdn_settings.png">
<br>
we enable websocket.
<br>
<img src="./ws_disabled.png">
Start the trial and it should look something like this
<br>
<img src="./ws_enabled.png">
<br>
Now lets add VCL for HTTP Connection Upgrade(Since we want to switch to Websocket)
<img src="./vcl.png" alt="">
<br>
<img src="./upgr.png" alt="">
<pre><code class="nim">
if (req.http.Upgrade) {
return (upgrade);
}
</code>
</pre>
</p>
</div>
</div><!-- /row -->
</div> <!-- /container -->
</div><!-- /white -->
<div id="anon2">
<div class="container">
<div class="row">
<div class="col-lg-8 col-lg-offset-2">
<h2><b>Testing Config</b></h2>
In this section we'll discuss how to connect to the prementioned setup using domain fronting technique.
<ul>
<li>
<h3><u>Linux</u></h3>
<p>
Copy the server config from panel(by clicking the qr-code) to clipboard.
<br>
Open client app(v2rayN/nekoray)
<br>
Ctrl + V
<br>
and edit it as follows.
<br>
For testing in Linux we are using v2rayN
</p>
<img src="./test_vmess.png" alt="">
<br><br>
click <b>Confirm</b>
<br><br>
If the connection was successful you'll see your server IP along with delay(ms) in the logs as well as on bottom right corner like this.
<img src="./connect_success.png" width="100%">
<br>
You could toggle System Proxy to check connectivity, within browser and all.
<br>
<img src="./system_proxy.png" alt="">
<br>
<br>
</li>
<li>
<h3><u>Android</u></h3>
<p></p>
</ul>
<h2><b>Testing Tor</b></h2>
<p>
<br><br>
go to
<b>about:preferences#connection</b>
change proxy settings as follows.
<br>
(Proxy port shown in v2ray.
So that connection made by tor will go through v2ray server)
<img src="./tor_proxy_settings.png" alt="">
<br>
<blockquote>
If we were to save it and try to connect <b>it will fail</b>.
(connection died in state handshaking).
<b>So enable Bridges</b>
</blockquote>
Set Bridges of Your Choice
<br>
<img src="./bridge.png" width="100%">
<br>
Thats It!
<br><br>
This is how the traffic leaves the system.
<br>
<img src="./ws_traffic.png" width="100%">
<br><br>
As you could see, traffic goes to fastly server rather than tor nodes.
<br>(Youre seeing Websocket traffic to and from 192.168.1.2(LAN IP) to a Fastly CDN(Anycast IP))
</p>
</div>
</div>
</div>
</div>
<!-- +++++ Footer Section +++++ -->
<div id="anonb">