Compare commits

...

4 Commits

Author SHA1 Message Date
coja 2076557875 [Sumadija] doc corrections 2026-08-09 04:23:12 +02:00
coja 00c1bb8b20 [Sumadija] doc addresses 2026-08-09 04:16:14 +02:00
coja 8d6025bcf3 [Sumadija] doc template 2026-08-09 04:10:17 +02:00
coja 491ba60d3c [Forum] update changelogs 2026-08-09 03:58:57 +02:00
10 changed files with 136 additions and 65 deletions
+9 -25
View File
@@ -18,29 +18,13 @@ VMID: 119
`/var/discourse_docker/discourse_doctor`
## Docker rebuild errors
`/var/discourse_docker/launcher rebuild web_only`
```
Plugin name is 'ldap', but plugin directory is named 'discourse-ldap-auth'
rake aborted!
ActiveRecord::NoDatabaseError: We could not find your database: discoursedb. Available database configurations can be found in config/database.yml. (ActiveRecord::NoDatabaseError)
```
```
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 593 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.3.0/lib/pups/exec_command.rb:131:in `spawn'
exec failed with the params {"cd"=>"$home", "tag"=>"migrate", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]}
bootstrap failed with exit code 1
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
a9a704b1ee166487d8cd2acd5bd9bcc050ed0ec93fc065f58440e4ae208e1937
```
Latest update:
- The forum has been restored; images should load when clicked but may not display immediately.
- Resolved several problems sequentially: admin panel and updates were failing, Docker builds failed due to PostgreSQL 13, upgraded to 15.
- Restored from backup and created a new backup from the old SQL server, transferring data via PostgreSQL 15.
- Manually enabled the required vector extension on the new database because Discourse could not do it automatically.
- Docker container rebuild succeeded only after disabling the SSL template in the Docker configuration.
- After rebuild, the forum returned with new posts but login failed and media/files were missing.
- Uploaded files after May 1 were lost; database and uploads backups were found in the shared folder.
- Login issue was caused by a missing SSL template; resolved by setting up an Nginx reverseproxy with a selfsigned certificate on the forum VM, allowing SSL access through the main HTTP VM.
+25 -19
View File
@@ -1,29 +1,35 @@
# List of containers
# Service Catalog: sumadijamoxx
## sumadijamoxx
## 🛠️ Overview
ip is the same as a container ID
example
101 ssh12 -> 192.168.7.101
IP addresses follow the container ID pattern:
`101 ssh12` -> `192.168.7.101`
VMID Name
101 ssh12
102 nginxproxymanager12
103 searxng12
104 homepage12
105 privatebin13
106 librespeed-rust12
107 tor13
200 wireguard12
| VMID | Name | OS | Notes |
| :--- | :--- | :--- | :--- |
| [101](./ssh12/) | [ssh12](./ssh12/) | 12 | SSH Jump host |
| [102](./nginxproxymanager12/) | [nginxproxymanager12](./nginxproxymanager12/) | 12 | Proxy |
| [103](./searxng12/) | [searxng12](./searxng12/) | 12 | Search |
| [104](./homepage12/) | [homepage12](./homepage12/) | 12 | Dashboard |
| [105](./pastebin13/) | [pastebin13](./pastebin13/) | 13 | Pastebin |
| [106](./librespeed-rust12/) | [librespeed-rust12](./librespeed-rust12/) | 12 | Speedtest |
| [107](./tor13/) | [tor13](./tor13/) | 13 | Tor Onion Service |
| [200](./wireguard12/) | [wireguard12](./wireguard12/) | 12 | VPN |
##### Legend
12 -> debian 12
13 -> debian 13
- `12` -> Debian 12
- `13` -> Debian 13
## Forwareded ports
## 🌐 Forwarded Ports
192.168.7.243:443 -> 80
192.168.7.101:22 -> 22
- `192.168.7.243:443` -> `80`
- `192.168.7.101:22` -> `22`
## 🌐 Public URLs
- Website: https://sumadija.dmz.rs
- Pastebin: https://pastebin.dmz.rs
+21
View File
@@ -0,0 +1,21 @@
---
VMID: 109
---
# Nginx
**VMID:** 102
**OS/Version:** Debian 13
## 🌐 Connectivity
- **Local IP:** `192.168.7.109`
- **Internal Port:** `80`
- **External/Proxy URL:** `https://sumadija.dmz.rs`
- **Access Type:** Local / Public (via proxy)
## 🛠️ Details
- **Dependencies:** None
## 📝 Notes
- Forwarded to port 80 and 443.
@@ -1,9 +0,0 @@
---
VMID: 102
---
NgniX proxy manager built with [script](https://community-scripts.github.io/ProxmoxVE/scripts?id=nginxproxymanager)
Forwarded to port 80
+15 -2
View File
@@ -1,7 +1,20 @@
---
VMID: 105
---
# PrivateBin
PrivateBin instance built with [script](https://community-scripts.github.io/ProxmoxVE/scripts?id=privatebin)
**VMID:** 105
**OS/Version:** Debian 13
Not yet public/forwarded
## 🌐 Connectivity
- **Local IP:** `192.168.7.105`
- **Internal Port:** `[N/A]`
- **External/Proxy URL:** `https://pastebin.dmz.rs`
- **Access Type:** Forwarded
## 🛠️ Details
- **Built with:** [PrivateBin Proxmox Script](https://community-scripts.github.io/ProxmoxVE/scripts?id=privatebin)
- **Dependencies:** None
## 📝 Notes
- Not yet public/forwarded.
+16 -2
View File
@@ -1,3 +1,17 @@
TP Link (hopefully openWRT in future)
# Router
Router is inside the existing network for further forwarding, contact coja (best on xmpp)
**VMID:** [N/A]
**OS/Version:** TPLink (Hopefully OpenWRT in future)
## 🌐 Connectivity
- **Local IP:** 192.168.7.1
- **Internal Port:** `[N/A]`
- **External/Proxy URL:** `[N/A]`
- **Access Type:** Local
## 🛠️ Details
- **Built with:** N/A
## 📝 Notes
- Router is inside the existing network for further forwarding.
- Contact coja (best on xmpp) for access/info.
+14 -2
View File
@@ -1,8 +1,20 @@
---
VMID: 102
---
# SearXNG
SearXNG instance built with [script](https://community-scripts.github.io/ProxmoxVE/scripts?id=searxng)
**VMID:** 103
**OS/Version:** Debian 12
## 🌐 Connectivity
- **Local IP:** `192.168.7.103`
- **Internal Port:** `[N/A]`
- **External/Proxy URL:** `https://search.dmz.rs`
- **Access Type:** Local (Not yet public/forwarded)
Not yet public/forwarded
## 🛠️ Details
- **Built with:** [SearXNG Proxmox Script](https://community-scripts.github.io/ProxmoxVE/scripts?id=searxng)
- **Dependencies:** None
## 📝 Notes
- Not yet public/forwarded.
+18 -3
View File
@@ -1,9 +1,24 @@
---
VMID: 101
---
# SSH Gateway
SSH port from this container should be forwarded to sumadija.dmz.rs
SSH access to other containers is done through this one with ssh jump, passwords are disabled, so only keys verification is used.
**VMID:** 101
**OS/Version:** Debian 12
[wiki page](https://wiki.dmz.rs/en/sysadmin/ssh)
## 🌐 Connectivity
- **Local IP:** `192.168.7.101`
- **Internal Port:** `22`
- **External/Proxy URL:** `https://sumadija.dmz.rs`
- **Access Type:** Public (via SSH forwarding)
## 🛠️ Details
- **Built with:** N/A
- **Dependencies:** None
## 📝 Notes
- SSH port from this container should be forwarded to `sumadija.dmz.rs`.
- SSH access to other containers is done through this one with SSH jump.
- **Security:** Passwords are disabled; only key verification is used.
- [Wiki Guide](https://wiki.dmz.rs/en/sysadmin/ssh)
+18 -3
View File
@@ -1,9 +1,24 @@
---
VMID: 107
---
# Tor Onion Service
In this container hosts the tor onion service, used for remote access to the proxmox, through tor. Credentatials are in the password manager
**VMID:** 107
**OS/Version:** Debian 13
## 🌐 Connectivity
- **Local IP:** `192.168.7.107`
- **Internal Port:** `[N/A]`
- **External/Proxy URL:** `[Tor Onion Address]`
- **Access Type:** Public (via Tor)
ssh12 -> port 22
smoxx -> 8006
## 🛠️ Details
- **Built with:** N/A
- **Dependencies:** None
## 📝 Notes
- This container hosts the Tor onion service, used for remote access to Proxmox through Tor.
- **Credentials:** Stored in **dmzadmin** (password manager).
- **Remote access targets:**
- `ssh12` -> port 22
- `smoxx` -> port 8006