Hello! I'm using the Turnkey LAMP Stack image to operate a reverse proxy in my network infrastructure as a virtual machine on Microsoft's Hyper-V platform. I originally set up this reverse proxy with 2 network adapters/interface cards (NICs): one to speak to the outer web (WAN; on eth0) and one to speak to servers on the local network (LAN; on eth1). I've since changed the network settings beyond the scope of this virtual machine so it doesn't require the WAN NIC anymore, just the LAN, so I removed the WAN NIC in the virtual machine's Hyper-V settings.
Over on Reddit, u/Solnse asked about setting up a LAMP/LAPP appliance to host multiple sites via different domains. AKA "name based virtual hosts". I've tried 3 times to post this over there as a reply, but for some reason, Reddit just keeps giving me a vague error message?!? Maybe it's too long? Regardless, I've given up and am posting here instead.
I am attempting to make use of turnkey linux wordpress and am at a bit of a loss for how to configure SSL on the 'backend' vm with the wordpress-18.0-bookworm-amd64.iso
Just looking for some support/advice. Working on setting up the LE certs via confconsole. My name host is nsone however they only host one of my subdomains. The scripts appear to be calling ~api.nsone.com/zone/MY-TLD/, rather than my subdomain resulting in a 404 error.
I just installed Gitlab 18 in a VMware virtual machine. I want to use it only in the LAN, so I specified as domain the IP address that I then statically assigned to the machine, but I can't log in even as root user: the password is correct because if I get it wrong I get invalid login. Does anyone have an idea where I can at least check what is going wrong? Thanks in advance.
Every time I start to tinker with the security settings on this thing, I break it. So I've rebuilt my appliance (again) and rebuilt my wiki.. and manually migrated the content (since I couldn't get the migration process to work). So in an effort to not break this instance, I'm asking.
I use VisualEditor and need to not break it. Based on what I've read, this means that the entire wiki basically has to be unsecured for this to work. My goal is to secure the wiki - login required to view pages, visualeditor still functional. Running 18.0
I have just installed my first turnkey "debian-12-turnkey-nextcloud_18.0-1_amd64.tar.gz" from the Proxmox turnkey templates and am having a few issues regarding 2 security risks.