Moved to Wiki tab.
This commit is contained in:
Lucas Mathews
2
.gitignore
vendored
2
.gitignore
vendored
@@ -1,2 +0,0 @@
|
||||
# OR only to exclude workspace cache
|
||||
.obsidian
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 516 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 51 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 28 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 73 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 39 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 86 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 40 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 68 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 123 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 39 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 401 KiB |
10
Public.md
10
Public.md
@@ -1,10 +0,0 @@
|
||||
---
|
||||
title: Public
|
||||
description: Landing page for public content
|
||||
published: true
|
||||
tags: public
|
||||
editor: markdown
|
||||
---
|
||||
# Public Pages
|
||||
|
||||
Welcome! Here are the public guides:
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
title: Guides
|
||||
description: Landing page for Guides
|
||||
published: true
|
||||
tags: public
|
||||
editor: markdown
|
||||
---
|
||||
# Public Pages
|
||||
|
||||
Welcome! Here are the guides:
|
||||
@@ -1,28 +0,0 @@
|
||||
---
|
||||
title: Create SSH Keys in Gitea
|
||||
description:
|
||||
published: true
|
||||
date: 2025-05-04T11:42:39.943Z
|
||||
tags: git, public
|
||||
editor: markdown
|
||||
dateCreated: 2025-05-04T11:38:34.846Z
|
||||
---
|
||||
## Creating SSH Key
|
||||
Ideally the following steps are completed on the device and user which you want to allow the connection from, so it will be saved in their `~/.ssh` folder.
|
||||
|
||||
Run the following commands:
|
||||
```bash
|
||||
cd ~/.ssh
|
||||
ssh-keygen -t ed25519 -C "your_email@example.com"
|
||||
```
|
||||
> [!NOTE]
|
||||
> You can also use a name instead of the email address i.e. `"lucas-desktop"`
|
||||
|
||||
## Add Keys to ssh-agent
|
||||
Run the following command
|
||||
`ssh-add ~/.ssh/id_ed25519`
|
||||
|
||||
Replace `id_ed25519` in the command with the name of your private key file
|
||||
|
||||
## Add Public key to Gitea
|
||||
`cat` the contents of the public key and add it into Gitea under **Settings** > **SSH / GPG Keys** > **Add key**.
|
||||
@@ -1,61 +0,0 @@
|
||||
---
|
||||
title: Manually Generate Wireguard Peer in OPNsense
|
||||
description:
|
||||
published: false
|
||||
date: 2025-12-13T11:39:23.471Z
|
||||
tags: networking
|
||||
editor: markdown
|
||||
dateCreated: 2025-05-04T11:38:34.846Z
|
||||
---
|
||||
|
||||
# Manually Generate Wireguard Peer in OPNsense
|
||||
This guide details how to manually (not using the Peer Generator) generate a new Wireguard peer in OPNsense.
|
||||
|
||||
|
||||
## Requirements
|
||||
The `wireguard-tools` package must be installed to generate the public and private keys.
|
||||
|
||||
|
||||
|
||||
### 1. Create a Peer
|
||||
|
||||
1. Generate a new public and private key with
|
||||
`wg genkey | tee privatekey | wg pubkey > publickey`
|
||||
This will create two files in the current directory with the public and private key. Save these for later.
|
||||
|
||||
2. In the OPNsense UI go to VPN > Wireguard > Peers, and click the + to add a new peer
|
||||
|
||||
3. Fill in the details:
|
||||
- **Name**: Enter a name for the peer
|
||||
- **Public key**: Paste the public key you generated earlier
|
||||
- **Pre-shared key**: Generate a key if desired and save it for later
|
||||
- **Allowed IPs**: Specify the IP address or subnet that this peer is allowed to use (e.g., 10.0.60.2/32). Check your existing peers to ensure it is not already used
|
||||
- **Endpoint address**: Leave blank if the client will be roaming
|
||||
- **Endpoint port**: Leave blank
|
||||
- **Instances** Choose appropriate instance
|
||||
- **Keepalive**: Can be left blank
|
||||
|
||||
4. Save the Configuration
|
||||
|
||||
### 2. Create the Wireguard Config File
|
||||
|
||||
1. Create a new file called `<NAME>.conf`. You can choose the name.
|
||||
2. Copy and paste the contents from below into the file and update the values:
|
||||
```
|
||||
[Interface]
|
||||
PrivateKey = <private-key>
|
||||
Address = 10.0.60.2/32 # Use the same IP address or subnet specified in OPNsense
|
||||
DNS = 8.8.8.8 # Optional: Specify a DNS server, not required if only routing resources (not an Internet connection) or using DNS names.
|
||||
|
||||
[Peer]
|
||||
PublicKey = <opnsense-public-key>
|
||||
PresharedKey = <preshared-key> # Only needed if generated in previous step
|
||||
Endpoint = <opnsense-public-ip>:51820 # Replace with the OPNsense public IP and port
|
||||
AllowedIPs = 0.0.0.0/0 # Route all traffic through the VPN
|
||||
```
|
||||
|
||||
Replace `private-key`, `opnsense-public-key`, `preshared-key`, and `opnsense-public-ip` with the appropriate values.
|
||||
|
||||
For `AllowedIPs`, setting `0.0.0.0/0` will route all IPv4 addresses via the VPN connection. If only access to resources and no internet connection is required, the subnets can be added here i.e. `10.0.60.0/24, 10.0.70.0/24`
|
||||
|
||||
4. Import the `.conf` file into the VPN connection settings on the client device and test the connection.
|
||||
@@ -1,19 +0,0 @@
|
||||
---
|
||||
title: RDP to a Windows PC with a Microsoft Account
|
||||
description:
|
||||
published: true
|
||||
date: 2025-01-16T20:32:15.978Z
|
||||
tags: public, windows
|
||||
editor: markdown
|
||||
dateCreated: 2025-01-16T20:32:03.050Z
|
||||
---
|
||||
|
||||
# RDP with a Microsoft Account
|
||||
|
||||
Windows allows you to log in with only your Microsoft account email and your Microsoft Authenticator app. If you then want to RDP to this computer with the same Microsoft account your password will not be cached locally.
|
||||
|
||||
To add it to the cache, follow the below steps:
|
||||
|
||||
1. Open a new terminal window
|
||||
2. Enter the command `runas /u:MicrosoftAccount\[my account] cmd.exe`
|
||||
3. You can now use your email and Microsoft password to RDP to the computer.
|
||||
@@ -1,177 +0,0 @@
|
||||
---
|
||||
title: Reverse Proxy using a VPS
|
||||
description: Self hosted VPS as a Reverse Proxy
|
||||
published: true
|
||||
date: 2025-12-13T12:40:51.346Z
|
||||
tags: public, networking
|
||||
editor: markdown
|
||||
dateCreated: 2023-10-18T18:42:56.780Z
|
||||
---
|
||||
|
||||
This is a guide to create a reverse proxy using a Virtual Private Server, or VPS so that you can access internally hosted services.
|
||||
|
||||
# My Situation
|
||||
|
||||
I host some services from my home lab that I access remotely, such as Home Assistant.
|
||||
|
||||
In my previous house, I was the account owner for the internet. I was able to get a static IP, and have the ISP open incoming ports 80 and 443 for web traffic.
|
||||
|
||||
Now I lived in shared accommodation which has an included internet connection, in the form of an Ethernet cable coming out the wall. Everyone just uses the same LAN.
|
||||
I do have access to the router, but to maintain an environment that I can ‘home lab freely' in, I wanted to set up my own LAN.
|
||||
|
||||
I can do this while still utilising the shared connection. We have fiber and my services are not bandwidth heavy.
|
||||
|
||||
I have configured a router of my own with, with all traffic sent via [Mullvad VPN](https://mullvad.net/en).
|
||||
|
||||
Now I need to be able to access my internal services externally, using this same internet connection.
|
||||
|
||||
# The Plan
|
||||
|
||||
There are some ways I can do this:
|
||||
|
||||
- A VPN to my network, such as OpenVPN, SSL VPN, WireGuard, or even an overlay network such as TailScale.
|
||||
This however this would mean I have to install a VPN app first and configure it. What if someone else wants to watch videos too? They now have to install some VPN app on their TV. Too much work! I just want to be able to browse to a domain to access the site.
|
||||
- Get a VPN provider with a static IP. This is not ideal as most VPN providers do not provide static IPs, and if they do, they are quite costly.
|
||||
- Use a [Cloudflare Tunnel](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/). I have used this in past, it is free, however it is not overly well suited for streaming video.
|
||||
I am working towards a goal of being able to stream 4k video remotely.
|
||||
|
||||
Instead, I am going to build my own cloud reverse proxy host.
|
||||
|
||||
This makes use of a Virtual Private Server (VPS) to run Nginx Reverse Proxy Manager. The VPS will have access to the services running on my internal network via a WireGuard VPN.
|
||||
|
||||
This will connect to my home network with a WireGuard VPN, and will run Reverse Proxy Manager to manage incoming web connections.
|
||||
|
||||
To make this, I need a few things:
|
||||
|
||||
1. A VPS. There are many to choose from. In the end I went with a server from [OVHcloud](https://www.ovhcloud.com/en/).
|
||||
- WireGuard is efficient compared to other VPN protocols, so the server does not have to be too powerful.
|
||||
- Be sure to check how much network traffic the VPS allows. Lots have limits, which may or may not be enough for your use case. I am streaming 4k video so I am looking for unlimited bandwidth.
|
||||
2. A router that allows for new VPN interfaces to be created. I use [opnSense](https://opnsense.org/) for my router which does allow this.
|
||||
|
||||
# VPS Setup
|
||||
|
||||
First I need to find a VPS provider. As I said before, I went with a server from [OVHcloud](https://www.ovhcloud.com/en/).
|
||||
|
||||
The server I chose (VLE-4) costs $11 US per month.
|
||||
|
||||
- 4 vCores
|
||||
- 4GB RAM
|
||||
- 80 GB NVMe SSD
|
||||
- 1 Gbps unmetered connection
|
||||
- 1x Static IPv4 address
|
||||
- Anti-DDoS Protection Included
|
||||
- Ubuntu 23.04
|
||||
|
||||
Once I purchased the server and it had provisioned, I connected and set up a few things.
|
||||
|
||||
1. Updated to Ubuntu 23.10
|
||||
2. Enabled Key-Based only login: See this guide: [How To Configure SSH Key-Based Authentication on a Linux Server](https://www.digitalocean.com/community/tutorials/how-to-configure-ssh-key-based-authentication-on-a-linux-server)
|
||||
3. Enable UFW Firewall
|
||||
- Allow port 22(SSH), 51820/UDP(WireGuard), 443(HTTPS)
|
||||
`sudo ufw allow <PORTS>`
|
||||
- Enable UFW
|
||||
`sudo ufw enable`
|
||||
4. Enabled the edge firewall on my hosting provider.
|
||||
|
||||
# VPN Setup
|
||||
|
||||
After this it is time to install WireGuard VPN on the VPS.
|
||||
|
||||
For this, I mostly followed this guide: [How To Set Up WireGuard on Ubuntu 20.04](https://www.digitalocean.com/community/tutorials/how-to-set-up-wireguard-on-ubuntu-20-04)
|
||||
|
||||
I recommend reading that guide as there are some decisions I made that I do not explain, but at a high level, I followed through the steps up to the end of step 6:
|
||||
|
||||
- Install WireGurad
|
||||
- Create a new WireGuard private and public key pair:
|
||||
`wg genkey | sudo tee /etc/wireguard/private.key`
|
||||
`sudo cat /etc/wireguard/private.key | wg pubkey | sudo tee /etc/wireguard/public.key`
|
||||
- Chose a new IP range, I chose 10.0.20.0/24
|
||||
- Created a new WireGuard Configuration file:
|
||||
`/etc/wireguard/wg0.conf`
|
||||
|
||||
I was then able to start the WireGuard server, however I have still not yet added any peers. The guide explains how to do this on another Linux server, but in this case, I do not want to do that. Instead of step 7:
|
||||
|
||||
This is done in the WireGuard Instance settings in my Router:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Be sure to check the ‘Disable routes’ option in the Instance, as I will do this manually
|
||||
For the gateway, it does not matter, just as long as it is unique.
|
||||
|
||||
Then in the Peers tab:
|
||||
|
||||
The Pubic Key is the Public key from the WireGuard Server on the VPS
|
||||
|
||||
The Endpoint Address is the public IP of the VPS.
|
||||
|
||||
|
||||
|
||||
After this we can continue with the [Digital Ocean guide](https://www.digitalocean.com/community/tutorials/how-to-set-up-wireguard-on-ubuntu-20-04) from step 8.
|
||||
|
||||
The below command is then run to add the new opnSense peer to the Wireguard server.
|
||||
|
||||
`sudo wg set wg0 peer <PUBLIC KEY> allowed-ips 10.0.20.2`
|
||||
|
||||
After doing this, I can see the VPN connection is up:
|
||||
|
||||
|
||||
|
||||
In the end, my /etc/wireguard/wg0.conf file looked like:
|
||||
|
||||
```plaintext
|
||||
[Interface]
|
||||
Address = 10.0.20.1/24
|
||||
SaveConfig = true
|
||||
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
|
||||
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
|
||||
ListenPort = 51822
|
||||
PrivateKey = <SERVER PRIVATE KEY>
|
||||
|
||||
[Peer]
|
||||
PublicKey = <PEER PUBLIC KEY>
|
||||
AllowedIPs = 10.0.20.0/24, 10.0.10.0/24
|
||||
PersistentKeepalive = 25
|
||||
```
|
||||
|
||||
# Network Setup
|
||||
|
||||
Now an interface needs to be created on my router for the new VPN connection so that I can configure firewall rules to allow and deny access.
|
||||
|
||||
For opnSense, this is as simple as going to Interfaces > Assignments, and adding the new interface
|
||||
|
||||
|
||||
|
||||
Then configure the settings as below:
|
||||
|
||||
|
||||
|
||||
You do not need to configure a IPv4 address, as this will automatically get the IP address specified of the Instance Tunnel Address.
|
||||
|
||||
After this, I created the below firewall rule so that the new WireGuard interface could access the LAN.
|
||||
|
||||
|
||||
|
||||
If you have any strange issues, check the routing table (System > Routes > Status) to see if there are any old entries that need to be deleted.
|
||||
|
||||
# Reverse Proxy
|
||||
|
||||
For the reverse Proxy I am using [Nginx Reverse Proxy Manager](https://nginxproxymanager.com/) running in a Docker container.
|
||||
|
||||
First, install Docker: [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/)
|
||||
|
||||
Then I installed Portainer to give a nice webUI to manage Docker: [Install Portainer CE with Docker on Linux](https://docs.portainer.io/start/install-ce/server/docker/linux)
|
||||
|
||||
Then in Portainer I made a new stack (docker compose).
|
||||
|
||||
|
||||
|
||||
I was then able to log into Reverse Proxy Manager and create the my domains in Reverse Proxy Manager
|
||||
|
||||
|
||||
|
||||
I also needed to point these domains to the public IP of my VPS.
|
||||
|
||||
Once this was done, I was able to access the internal services via my domain name.
|
||||
For example, this website!
|
||||
File diff suppressed because one or more lines are too long
@@ -1,43 +0,0 @@
|
||||
---
|
||||
title: Blank Template
|
||||
description:
|
||||
published: false
|
||||
date: 2025-05-04T11:42:39.943Z
|
||||
tags: private, template
|
||||
editor: markdown
|
||||
dateCreated: 2025-05-04T11:38:34.846Z
|
||||
---
|
||||
|
||||
# About this template
|
||||
This template is intended to be used for creating new Wiki.js entries from Obsidian, which has a Git sync to the same repo that Wiki.js is synced with.
|
||||
|
||||
Simple creating and sorting of Wiki entries from here can be done via creating files in the appropriate directories here and adjusting the properties. Use markdown format.
|
||||
|
||||
|
||||
There are some important things to note:
|
||||
|
||||
## Directories
|
||||
### Guides
|
||||
This is a public directory. When files are put here, anyone
|
||||
|
||||
### Images
|
||||
Contains all of the images that are referenced in Wiki articles.
|
||||
|
||||
## Tags
|
||||
Tags in the properties field above must be in the below format:
|
||||
`tag1, tag2, tag3` i.e. csv
|
||||
|
||||
However the Obsidian viewer uses a list format:
|
||||
```txt
|
||||
tags:
|
||||
- tag1
|
||||
- tag2
|
||||
- tag3
|
||||
```
|
||||
|
||||
So in Obsidian, you will see an error in the visual editor:
|
||||
|
||||
Tags can be created here and will be added to the Tags list in Wiki.js.
|
||||
|
||||
## Images
|
||||
Images just work as standard. Store all images in the `_images` folder, which is backed up to the [lucas-wiki](https://git.lucasmathews.com/lucas/lucas-wiki) repository, but hidden for users in Wiki.js.
|
||||
29
home.md
29
home.md
@@ -1,29 +0,0 @@
|
||||
---
|
||||
title: homepage
|
||||
description:
|
||||
published: true
|
||||
date: 2025-12-23T13:48:08.995Z
|
||||
tags: public
|
||||
editor: markdown
|
||||
dateCreated: 2025-12-23T13:48:08.994Z
|
||||
---
|
||||
|
||||
# Welcome to my Wiki
|
||||
|
||||
|
||||
|
||||
This site contains various articles and guides written by myself.
|
||||
|
||||
This is partly for my reference, as well as provide insight into my home lab and the projects I do around this.
|
||||
Others may come across these guides when trying to search how to do something - a place where I find myself often, and i always appreciate it when others make guides that assist me with my projects. There may also be some content here that I created in my university studies or work.
|
||||
|
||||
Please note that all work here is not intended to be definitive, and may not be best practice. Please combine my work with your own investigations.
|
||||
All content posted here is welcome to scrutinization.
|
||||
|
||||
For an overview of exactly what I work on, here is a network diagram:
|
||||
|
||||
|
||||
|
||||
# Site Content
|
||||
|
||||
There is not much available here at the moment, check back later!
|
||||
Reference in New Issue
Block a user