vh/NetAlertX
1
0
Fork 0
mirror of https://github.com/jokob-sk/NetAlertX.git synced 2025-12-07 09:36:05 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Numbering sequence corrected

Browse Source
This commit is contained in:
Ingo Ratsdorf
2025-09-12 15:40:51 +12:00
parent e00f26658b
commit 8f00a28454
1 changed files with 24 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
docs/REVERSE_PROXY.md
View File

@@ -56,13 +56,13 @@
} }
``` ```
4. Check your config with `nginx -t`. If there are any issues, it will tell you. 3. Check your config with `nginx -t`. If there are any issues, it will tell you.
5. Activate the new website by running the following command: 4. Activate the new website by running the following command:
`nginx -s reload` or `systemctl restart nginx` `nginx -s reload` or `systemctl restart nginx`
6. Once NGINX restarts, you should be able to access the proxy website at http://netalertx/netalertx/ 5. Once NGINX restarts, you should be able to access the proxy website at http://netalertx/netalertx/
<br/> <br/>
@@ -123,13 +123,13 @@
} }
``` ```
4. Check your config with `nginx -t`. If there are any issues, it will tell you. 3. Check your config with `nginx -t`. If there are any issues, it will tell you.
5. Activate the new website by running the following command: 4. Activate the new website by running the following command:
`nginx -s reload` or `systemctl restart nginx` `nginx -s reload` or `systemctl restart nginx`
6. Once NGINX restarts, you should be able to access the proxy website at https://netalertx/ 5. Once NGINX restarts, you should be able to access the proxy website at https://netalertx/
<br/> <br/>
@@ -155,13 +155,13 @@
} }
``` ```
4. Check your config with `nginx -t`. If there are any issues, it will tell you. 3. Check your config with `nginx -t`. If there are any issues, it will tell you.
5. Activate the new website by running the following command: 4. Activate the new website by running the following command:
`nginx -s reload` or `systemctl restart nginx` `nginx -s reload` or `systemctl restart nginx`
6. Once NGINX restarts, you should be able to access the proxy website at https://netalertx/netalertx/ 5. Once NGINX restarts, you should be able to access the proxy website at https://netalertx/netalertx/
<br/> <br/>
@@ -195,13 +195,13 @@
} }
``` ```
4. Check your config with `nginx -t`. If there are any issues, it will tell you. 3. Check your config with `nginx -t`. If there are any issues, it will tell you.
5. Activate the new website by running the following command: 4. Activate the new website by running the following command:
`nginx -s reload` or `systemctl restart nginx` `nginx -s reload` or `systemctl restart nginx`
6. Once NGINX restarts, you should be able to access the proxy website at https://netalertx/netalertx/ 5. Once NGINX restarts, you should be able to access the proxy website at https://netalertx/netalertx/
<br/> <br/>
@@ -220,13 +220,13 @@
</VirtualHost> </VirtualHost>
``` ```
4. Check your config with `httpd -t` (or `apache2ctl -t` on Debian/Ubuntu). If there are any issues, it will tell you. 3. Check your config with `httpd -t` (or `apache2ctl -t` on Debian/Ubuntu). If there are any issues, it will tell you.
5. Activate the new website by running the following command: 4. Activate the new website by running the following command:
`a2ensite netalertx` or `service apache2 reload` `a2ensite netalertx` or `service apache2 reload`
6. Once Apache restarts, you should be able to access the proxy website at http://netalertx/ 5. Once Apache restarts, you should be able to access the proxy website at http://netalertx/
<br/> <br/>
@@ -247,13 +247,13 @@
</VirtualHost> </VirtualHost>
``` ```
4. Check your config with `httpd -t` (or `apache2ctl -t` on Debian/Ubuntu). If there are any issues, it will tell you. 3. Check your config with `httpd -t` (or `apache2ctl -t` on Debian/Ubuntu). If there are any issues, it will tell you.
5. Activate the new website by running the following command: 4. Activate the new website by running the following command:
`a2ensite netalertx` or `service apache2 reload` `a2ensite netalertx` or `service apache2 reload`
6. Once Apache restarts, you should be able to access the proxy website at http://netalertx/ 5. Once Apache restarts, you should be able to access the proxy website at http://netalertx/
<br/> <br/>
@@ -275,13 +275,13 @@
</VirtualHost> </VirtualHost>
``` ```
4. Check your config with `httpd -t` (or `apache2ctl -t` on Debian/Ubuntu). If there are any issues, it will tell you. 3. Check your config with `httpd -t` (or `apache2ctl -t` on Debian/Ubuntu). If there are any issues, it will tell you.
5. Activate the new website by running the following command: 4. Activate the new website by running the following command:
`a2ensite netalertx` or `service apache2 reload` `a2ensite netalertx` or `service apache2 reload`
6. Once Apache restarts, you should be able to access the proxy website at https://netalertx/ 5. Once Apache restarts, you should be able to access the proxy website at https://netalertx/
<br/> <br/>
@@ -305,13 +305,13 @@
</VirtualHost> </VirtualHost>
``` ```
4. Check your config with `httpd -t` (or `apache2ctl -t` on Debian/Ubuntu). If there are any issues, it will tell you. 3. Check your config with `httpd -t` (or `apache2ctl -t` on Debian/Ubuntu). If there are any issues, it will tell you.
5. Activate the new website by running the following command: 4. Activate the new website by running the following command:
`a2ensite netalertx` or `service apache2 reload` `a2ensite netalertx` or `service apache2 reload`
6. Once Apache restarts, you should be able to access the proxy website at https://netalertx/netalertx/ 5. Once Apache restarts, you should be able to access the proxy website at https://netalertx/netalertx/
<br/> <br/>