Update theme

blog/2018-06-21-making-a-wifi-enabled-smart-air-humidifier/index.md

@@ -116,4 +116,6 @@ binary_sensor:
     pin:
       number: D5
       mode: INPUT
-```
+```
+
+<BlogDiscussions/>

blog/2019-02-15-smart-doorbell-with-xiaomi-aqara-button-and-google-home/index.md

@@ -49,4 +49,6 @@ Now we need to create a handler of the Aqara button in `automations.yaml`:
   - data:
       message: "Someone near your front door"
     service: notify.push
-```
+```
+
+<BlogDiscussions/>

blog/2019-02-21-home-assistant-presence-detection-with-google-wifi/index.md

@@ -134,4 +134,6 @@ Now we can rely on that group’s state to check if there is nobody home. I’ve
     service: notify.push
 ```
 
-That is all for now. Thanks for reading.
+That is all for now. Thanks for reading.
+
+<BlogDiscussions/>

blog/2020-11-10-using-variables-as-configuration-for-home-assistant-automation/index.md

@@ -208,4 +208,6 @@ Also, this automation should be able to run in parallel to make it possible to h
 ```yaml
   mode: parallel
   max: 10
-```
+```
+
+<BlogDiscussions/>

blog/2020-12-29-bed-presence-detection-with-aqara-window-and-door-sensor-and-a-cheap-car-part/index.md

@@ -40,4 +40,6 @@ binary_sensor:
         friendly_name: "Bed occupancy"
         device_class: occupancy
         value_template: "{{is_state('binary_sensor.bed_occupancy_door_side', 'off') or is_state('binary_sensor.bed_occupancy_window_side', 'off')}}"
-```
+```
+
+<BlogDiscussions/>

blog/2021-01-06-send-and-receive-sms-in-home-assistant-with-gsm-modem/index.md

@@ -42,4 +42,6 @@ action:
 
 ![Parsing action](parse_action.png)
 
-Here we are checking for the `engine is off` text in incoming SMS to perform some action. For example, to set the value of some `input_boolean`.
+Here we are checking for the `engine is off` text in incoming SMS to perform some action. For example, to set the value of some `input_boolean`.
+
+<BlogDiscussions/>

blog/2021-01-13-adding-wifi-power-control-to-an-integrated-amplifier/index.md

@@ -105,3 +105,5 @@ switch:
 ```
 
 That’s it for today. Thanks for reading.
+
+<BlogDiscussions/>

blog/2021-01-13-building-wifi-ir-remote-control-for-any-tv-with-esp8266-wemos-d1-mini-and-esphome/index.md

@@ -237,4 +237,6 @@ Before placing our power supply inside the TV we need to make sure it is isolate
 
 So the overall picture is looking like this:
 
-![](overview.png)
+![](overview.png)
+
+<BlogDiscussions/>

blog/2021-01-15-ir-code-reader-with-esp8266-wemos-d1-mini-and-esphome/index.md

@@ -85,4 +85,6 @@ Compile, flash, open logs and start firing into our device with your IR remote.
 [17:34:51][D][remote.samsung:055]: Received Samsung: data=0xE0E020DF
 ```
 
-You can now use this data with the ESPHome [Remote Transmitter](https://esphome.io/components/remote_transmitter.html) component to build, for example, something like [this](/2021-01-13-building-wifi-ir-remote-control-for-any-tv-with-esp8266-wemos-d1-mini-and-esphome/index.md).
+You can now use this data with the ESPHome [Remote Transmitter](https://esphome.io/components/remote_transmitter.html) component to build, for example, something like [this](/2021-01-13-building-wifi-ir-remote-control-for-any-tv-with-esp8266-wemos-d1-mini-and-esphome/index.md).
+
+<BlogDiscussions/>

blog/2021-01-15-using-stepper-motor-to-control-amplifier-volume-knob/index.md

@@ -120,4 +120,6 @@ Decreasing the volume action is the same, but with negative `target`:
 service: esphome.amplifier_set_volume
 data:
   target: -50
-```
+```
+
+<BlogDiscussions/>

blog/2023-10-31-hosting-ghost-blog-on-synology-nas/index.md

@@ -8,7 +8,7 @@ Do you want to know how and where RandomPlace is hosted? Or do you just want to
 
 :::info
 
-This post is from the past. From far away times when this website had another domain, another name and another hosting place. For current setup, please see [HomeLab](/docs/homelab).
+This post is from the past. From far away times when this website had another domain, another name and another hosting place.
 
 Still, this guide can be useful.
 
@@ -119,4 +119,6 @@ You'll get an email notification on the address added here when there will be ti
 
 After certificate generation, we should open Settings on the same Certificates tab, find our domain service, and choose the newly generated certificate for it.
 
-That's it!
+That's it!
+
+<BlogDiscussions/>

blog/2023-12-19-monitor-usb-ups-connected-to-synology-nas-in-home-assistant/index.md

@@ -43,4 +43,6 @@ In your Home Assistant go to _Settings -> Devices & services_ and click the _"Ad
 
 In the configuration window that appeared you need to set your NAS's local IP address as a _Host_ and leave the _Port_ number unchanged.
 
-Hit _Submit_ and you are done.
+Hit _Submit_ and you are done.
+
+<BlogDiscussions/>

blog/2023-12-19-restart-or-shutdown-your-proxmox-node-from-home-assistant-automation/index.md

@@ -54,4 +54,6 @@ The authorization header should have the next format: `PVEAPIToken=<proxmox user
 
 You can use `shutdown` or `reboot` as a `command`.
 
-After restarting Home Assistant you will have a new service available. In our example, it would be `rest_command.spacedock_one_shutdown`. Calling it will do the trick.
+After restarting Home Assistant you will have a new service available. In our example, it would be `rest_command.spacedock_one_shutdown`. Calling it will do the trick.
+
+<BlogDiscussions/>

blog/2025-02-15-wireguard-tunnel-from-ubuntu-vps-to-homelab-through-unifi-vpn-server/index.md

@@ -105,4 +105,6 @@ And up it back with a system service, also enabling it:
 sudo systemctl start wg-quick@wg0 && sudo systemctl enable wg-quick@wg0
 ```
 
-Further interface control should be performed through `systemctl` as well like `systemctrl stop`, `systemctl restart` or `systemctl status`.
+Further interface control should be performed through `systemctl` as well like `systemctrl stop`, `systemctl restart` or `systemctl status`.
+
+<BlogDiscussions/>

blog/2025-05-21-make-one-proxmox-node-to-wol-another/index.md

@@ -98,4 +98,6 @@ Cron job line to add:
 
 ```
 @reboot sleep 30s && /usr/sbin/etherwake -i vmbr0 <mac_address>
-```
+```
+
+<BlogDiscussions/>

blog/2025-10-07-proxmox-ve-on-hetzner-dedicated-server/index.md

@@ -0,0 +1,187 @@
+---
+slug: proxmox-ve-on-hetzner-dedicated-server
+title: "Proxmox VE and PBS on Hetzner dedicated server"
+tags: [self-hosting, homelab, Proxmox, Proxmox VE, PBS, Hetzner, Tailscale, Caddy]
+image: /img/homelab.png
+---
+
+Circumstances forced me to move all my self-hosted services to a location that does not depend on my living place. Someday, I hope I'll have all that hosted at home again, but now I want to describe my path of setting up a Proxmox VE on a Hetzner dedicated server together with Proxmox Backup Server and Tailscale with backups on Backblaze. This could look like a trivial task at first, but I faced some issues and obstacles I want to document here, for me to remember and for others to be informed.
+
+I want to warn that this is not a full step-by-step guide. It is rather notes on the process and steps I followed.
+
+<!-- truncate -->
+
+## Installation
+
+There is documentation on the installation process at [Hetzner](https://community.hetzner.com/tutorials/install-and-configure-proxmox_ve). There are options, and I chose the first one - installing Proxmox VE on Debian.
+So, according to the docs, I booted a [Rescue System](https://docs.hetzner.com/robot/dedicated-server/troubleshooting/hetzner-rescue-system/) and installed Debian with the [installimage](https://docs.hetzner.com/robot/dedicated-server/operating-systems/installimage/).
+Then I followed the [guide from Proxmox Wiki](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie) to install Proxmox VE. There is a step where you first install a new kernel and reboot to activate it. I was forced to reboot the server twice to make it appear online again. Have no idea why.
+
+## Network
+
+Now to the hard part.
+The initial plan was to have all LXCs in a single local network to allow internal communication. Also, the host and some containers should have public IPs for external access.
+
+I reviewed a lot of network configuration options around the internet and chose a bridged setup with masquerading (NAT).
+
+For the network I edited `/etc/network/interfaces` like this:
+
+```
+auto lo
+
+iface lo inet loopback
+
+iface lo inet6 loopback
+
+iface enp5s0 inet manual
+
+iface enp5s0 inet6 manual
+
+auto vmbr0
+iface vmbr0 inet static
+        address <Public IPv4>/26
+        gateway <Public IPv4 gateway>
+        pointopoint <Public IPv4 gateway>
+        bridge-ports enp5s0
+        bridge-stp off
+        bridge-fd 0
+        up route add -net <Public IPv4 gateway - 1> netmask 255.255.255.192 gw <Public IPv4 gateway> dev vmbr0
+        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
+        post-up echo 1 > /proc/sys/net/ipv6/conf/all/forwarding
+        post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp -d <Public IPv4> --dport 21074 -j DNAT --to 192.168.50.3
+        post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp -d <Public IPv4> --dport 21074 -j DNAT --to 192.168.50.3
+
+iface vmbr0 inet6 static
+        address <Public IPv6>/64
+        gateway <Public IPv6 gateway>
+
+auto vmbr1
+iface vmbr1 inet static
+        address 192.168.50.1/24
+        netmask  255.255.255.0
+        bridge-ports none
+        bridge-stp off
+        bridge-fd 0
+        post-up   iptables -t raw -I PREROUTING -i fwbr+ -j CT --zone 1
+        post-down iptables -t raw -D PREROUTING -i fwbr+ -j CT --zone 1
+        post-up iptables -t nat -A POSTROUTING -s '192.168.50.0/24' -o vmbr0 -j MASQUERADE
+        post-down iptables -t nat -D POSTROUTING -s '192.168.50.0/24' -o vmbr0 -j MASQUERADE
+```
+
+Let's see what's going on in here.
+
+For the containers that don't require a public IP, I choose `vbmr1` bridge, set some IP from the local IP range (192.168.50.x), and use host local IP as a gateway:
+
+![LXC local network](vmbr1.png)
+
+For LXCs that require a separate public IP, I choose the `vmbr0` bridge, set the IP, gateway, and MAC address provided by Hetzner.
+
+![LXC public network](vmbr0.png)
+
+The route with the `<Public IPv4 gateway - 1>` is a route from the official [Hetzner docs](https://community.hetzner.com/tutorials/install-and-configure-proxmox_ve). That doc was updated while I was writing this post, and the line was removed from the example network configuration there. Some network configuration guides across the internet still have it, so I'm leaving it as is for now. If your public IP gateway is, for example, 67.11.34.23, the route will be
+
+```
+up route add -net 67.11.34.22 netmask 255.255.255.192 gw 67.11.34.23 dev vmbr0
+```
+
+The next lines enable IP forwarding across networks:
+
+```
+post-up echo 1 > /proc/sys/net/ipv4/ip_forward
+post-up echo 1 > /proc/sys/net/ipv6/conf/all/forwarding
+```
+
+And here is an example of forwarding a port `21074` from the public IP to the local IP of a single LXC:
+
+```
+post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp -d <Public IPv4> --dport 21074 -j DNAT --to 192.168.50.3
+post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp -d <Public IPv4> --dport 21074 -j DNAT --to 192.168.50.3
+```
+
+For the local network `vmbr1` the next lines are needed to make Proxmox Firewall work properly:
+
+```
+post-up   iptables -t raw -I PREROUTING -i fwbr+ -j CT --zone 1
+post-down iptables -t raw -D PREROUTING -i fwbr+ -j CT --zone 1
+```
+
+### Network security
+
+Ports `8006`, `22`, and `8007` are opened on the Proxmox host in the Proxmox firewall, but explicitly closed in the Hetzner firewall. That way, I can use Proxmox VE and PBS web UI only from the Tailscale network, but, in case of an emergency or misconfiguration, I can open critical ports in Hetzner firewall to get access using server's public IP.
+
+## Public Reverse Proxy
+
+I know it is not the best practice to install anything directly on a Proxmox host, but this looks like a perfect decision, as it already has a public IP address, and I can't unassign it because this is the only way to access the server in case of failure.
+So I decided to install Caddy directly to a Proxmox Host and open ports `80` and `443` to it. Caddy handles requests and then proxies them to the local IPs of LXCs:
+
+```
+git.nicelycomposed.codes {
+        reverse_proxy 192.168.50.3:3000
+}
+```
+
+## Tailscale and Internal Reverse Proxy
+
+They call it "bastion host". A single point of connecting to your internal resources that you don't want to expose publicly. I have an LXC for this with Tailscale and another instance of Caddy installed. Let's see how it works on an example.
+
+I want to securely connect to the Proxmox VE web UI using a valid SSL certificate at `https://pve.int.example.com`.
+
+First, to make Tailscale work inside an LXC, additional configuration should be made on the Proxmox host. LXC configuration file can be found at `/etc/pve/lxc/<CT_ID>.conf`. Those two lines should be added to the file:
+
+```
+lxc.cgroup2.devices.allow: c 10:200 rwm
+lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file
+```
+
+Then just restart the LXC.
+
+Then, I installed Tailscale and Caddy on my "bastion host". Then I created a DNS record to point `pve.int.example.com` to an IP address of my bastion host in the Tailscale network:
+
+```
+A      pve.int.example.com      10.11.12.13
+```
+
+Then, in the Caddy config, I proxied `pve.int.example.com` to the local IP of my Proxmox host and port `8006`, using HTTPS and skipping TLS verification because of Proxmox's default self-signed certificate:
+
+```
+pve.int.example.com {
+        reverse_proxy 192.168.50.1:8006 {
+                transport http {
+                        tls
+                        tls_insecure_skip_verify
+                }
+        }
+}
+```
+
+Now I'm able to point my browser to `https://pve.int.example.com` while connected to my Tailscale network.
+
+:::warning
+As all ports are closed on the "bastion host" and it is not exposed publicly, the default ACME HTTP challenge will not work for Caddy to issue SSL certificates for internal resources. [DNS challenge](https://caddyserver.com/docs/json/admin/identity/issuers/acme/challenges/) should be used instead.
+:::
+
+I can add other internal resources hosted on other LXCs in the same way:
+
+```
+dockge.int.example.com {
+        reverse_proxy 192.168.50.4:5000
+}
+
+element-admin.int.example.com {
+        reverse_proxy 192.168.50.8:8080
+}
+```
+
+## Proxmox Backup Server
+
+It was the simplest part. I know this is not the most recommended method, but my Proxmox Backup Server is [installed on the Proxmox VE host](https://pbs.proxmox.com/docs/installation.html#install-proxmox-backup-server-on-proxmox-ve).
+After installing it and configuring it to use [Backblaze S3 storage](https://pbs.proxmox.com/docs/storage.html#datastores-with-s3-backend), I just added it as a storage to Proxmox VE using the local IP of the host.
+
+![PBS config](pbs.png)
+
+## Conclusion
+Have no idea why everyone wants to write a conclusion for each post nowadays. It looks like a forced conclusion to a school physics problem in most cases: "Solving this problem of moving trains, we found out that trains can move".
+
+Have a nice tinkering.
+
+<BlogDiscussions/>

docusaurus.config.js

@@ -102,10 +102,10 @@ const config = {
         ],
       },
       footer: {
-        style: 'dark',
+        style: 'light',
         links: [
           {
-            title: 'This site sections',
+            title: 'This site sections:',
             items: [
               {
                 label: 'Blog',
@@ -121,7 +121,19 @@ const config = {
               },
             ],
           },
-
+          {
+            title: 'Feel free to contact me with questions and/or criticisms:',
+            items: [
+              {
+                label: 'Matrix',
+                to: 'https://matrix.to/#/@yehor:vi.place',
+              },
+              {
+                label: 'Mastodon',
+                to: 'https://techhub.social/@estevez',
+              },
+            ],
+          },
 
         ],
         copyright: `Copyright © ${new Date().getFullYear()} Yehor Vialov.`,

package.json

@@ -1,6 +1,6 @@
 {
   "name": "yevi-org",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",

src/components/BlogDiscussions/index.js

@@ -0,0 +1,16 @@
+import styles from './styles.module.css';
+
+export default function BlogDiscussions() {
+  const Svg = require('@site/static/icons/matrix.svg').default;
+
+  return (
+    <section className={styles.blogDiscussions}>
+
+      <a className={styles.blogDiscussions_container} href="https://matrix.to/#/%23yevi-org-pub:vi.place" target='_blank'>
+        <Svg fill="currentColor" className={styles.icon} role="img" />
+        <span className={styles.linkText}>Join discussion at Matrix</span>
+      </a>
+
+    </section>
+  );
+}

src/components/BlogDiscussions/styles.module.css

@@ -0,0 +1,27 @@
+.blogDiscussions {
+  display: flex;
+  flex-direction: row;
+  justify-content: center;
+  padding: 1rem 0;
+}
+
+.blogDiscussions_container {
+  display: flex;
+  flex-direction: row;
+  flex-wrap: wrap;
+  justify-content: center;
+  align-items: center;
+}
+
+.linkText {
+  width: 12rem;
+}
+
+.icon {
+  width: 3rem;
+  height: 3rem;
+}
+
+.icon path {
+  fill: var(--ifm-link-color) !important;
+}

src/components/HomepageFeatures/index.js

@@ -39,7 +39,17 @@ const FeatureList = [
     Svg: require('@site/static/icons/matrix.svg').default,
     description: (
       <>
-        If you want to chat
+        If you want to chat (with end-to-end encryption)
+      </>
+    ),
+  },
+  {
+    title: 'Pixelfed',
+    link: 'https://pixelfed.social/estevez',
+    Svg: require('@site/static/icons/pixelfed.svg').default,
+    description: (
+      <>
+        For some photography
       </>
     ),
   },
@@ -78,7 +88,7 @@ const FeatureList = [
 function Feature({ Svg, title, link, description }) {
   return (
 
-    <div className={clsx('col col--3')}>
+    <div className={clsx('col col--3', styles.featureBlock)}>
       <div className="text--center">
         <a href={link} target='_blank' className={styles.featureLink}>
           <Svg fill="currentColor" className={styles.featureSvg} role="img" />

src/components/HomepageFeatures/styles.module.css

@@ -5,15 +5,35 @@
   width: 100%;
 }
 
+.featureBlock {
+  padding-bottom: 1rem;
+}
+
+@media (max-width: 996px) {
+  .featureBlock {
+    --ifm-col-width: 50%;
+  }
+}
+
+@media (max-width: 500px) {
+  .featureBlock {
+    --ifm-col-width: 100%;
+  }
+}
+
 .featureSvg {
-  height: 100px;
-  width: 100px;
+  height: 60px;
+  width: 60px;
 }
 
 .featureSvg path {
   fill: var(--ifm-link-color) !important;
 }
 
+.featureBlock:hover .featureSvg path {
+  opacity: 0.7;
+}
+
 .featureLink {
   display: contents;
   color: unset;
@@ -27,4 +47,8 @@
 .featureLink:visited {
   text-decoration: none;
   color: unset;
+}
+
+.featureLink p {
+  color: var(--ifm-color-secondary-contrast-foreground);
 }

src/css/custom.css

@@ -16,7 +16,13 @@
   --ifm-code-font-size: 95%;
   --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.1);
   --ifm-footer-link-hover-color: #b07ab0;
-  --ifm-link-color: var(--ifm-color-primary-lightest)
+  --ifm-link-color: var(--ifm-color-primary-lightest);
+  --ifm-global-shadow-lw: 0 1px 2px 0 #541d5428;
+}
+
+.hero--primary {
+  --ifm-hero-background-color: transparent;
+  --ifm-hero-text-color: var(--ifm-font-color-base);
 }
 
 /* For readability concerns, you should choose a lighter palette in dark mode. */
@@ -30,4 +36,8 @@
   --ifm-color-primary-lightest: #d1b2d1;
   --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.3);
   --ifm-link-color: var(--ifm-color-primary-darker);
+}
+
+.hero {
+  border-bottom: 2px solid var(--ifm-color-primary-opaque-2);
 }

src/pages/index.js

@@ -15,7 +15,7 @@ function HomepageHeader() {
         <Heading as="h1" className="hero__title">
           Yehor Vialov
         </Heading>
-        <p className="hero__subtitle">Public Profiles</p>
+        <p className="hero__subtitle">Public profiles and publications</p>
         {/* <div className={styles.buttons}>
           <Link
             className="button button--secondary button--lg"

src/theme/MDXComponents.js

@@ -0,0 +1,13 @@
+import React from 'react';
+// Import the original mapper
+import MDXComponents from '@theme-original/MDXComponents';
+//Import custom component
+import BlogDiscussions from '@site/src/components/BlogDiscussions';
+
+export default {
+    // Re-use the default mapping
+    ...MDXComponents,
+    // Map the "<BlogDiscussions>" tag to our BlogDiscussions component
+    // `BlogDiscussions` will receive all props that were passed to `<BlogDiscussions>` in MDX
+    BlogDiscussions,
+};

static/icons/pixelfed.svg

@@ -0,0 +1,7 @@
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
+
+<!-- Uploaded to: SVG Repo, www.svgrepo.com, Transformed by: SVG Repo Mixer Tools -->
+<svg width="800px" height="800px" viewBox="-10 -5 1034 1034" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" fill="#000000">
+
+<g id="SVGRepo_bgCarrier" stroke-width="0"/>
+