I'm trialling the Mattermost appliance running in a VirtualBox VM. Everything work fine from the internal lan but I can't get access from the internet. Checking with browser as well as Mattermost app.
I have two bridged virtual nics in the VM, one on an internal lan and one directly connected to the firewall/router. The firewall has port 443 forwarded to the VM nic address. I've confirmed that this is open - pentest-tools.com can see that nginx is behind the port.
Seems I landed here in the middle of a site upgrade. Tried to download the Zurmo CRM virtual machine this morning, but the links at souceforge don't work. Status?
I've been trying to figure out how to solve this without success, maybe I'm missing something.
I have a turnkey virtual appliance with wordpress as an intranet since a couple of years, we can access it on the local network and through a VPN connection. I've recently deployed two more appliances, OTRS (finally installed osticket over) and redmine for ticketing and project management, but I can't access the last two through VPN.
Discovered the Wordpress Turnkey Appliance and love it! Was setting up some IP based virtual servers, and no matter what, when using the FQDN it automaticaly directs the clients to the /var/www/wordpress directory.
Is there something baked in the image that would cause this?
title says it all really I have gone through some kind of setup in windows 10, and it gave me a generated password that I am supposed to give to all other users in my domain... but I do not know where that password goes in the samba config.... there are so many settings and stuff I am totally lost.
So I got my music server running 9 months ago, as a newbie. During that time, I didn't need to do anything with TKL (as planned) so I am still a newbie! A problem developed with the external USB drive, which I have now replaced. In the process of rather clumsy unmounting, remounting, testing and rebooting via the web interface, I have ended up with a device which the system is looking for, but which is not there. When booting up, the system waits for 1.5 minutes for a response from this non-existent device and then goes into emergency mode and the web interface is not available.