Twinky

virtual hosts need their own way of being recognised - a shared IP address among 6 virtual hosts won't work.. So you use a name - a domain name. A few problems.. you need a different one for each host (or subdomains) and you need to register them.. You also need to setup apache to handle them (plenty of guides online for that). The REAL problem though is that if you want to access them over a local network then you need two things: domain (either locally hosted or via a public dns) and a proper dns setup in your windows machines. So.. I chose to have local names - like home.lan, admin.lan, inventory.lan... To use them apache has to be configured. Then you need a local dns nameserver on your webserver PC - setup those domains on there and it will serve any local requests with the IP address of your apache enabled pc. The real issue though is that for many networks you'd need to then reconfigure every devices dns settings. If they're all on dynamic IP address's it's easier to use a dhcp server - when each device requests it's IP address the dhcp server can also reply with the ip address of a dns server to use - in this case the one you have your domains on. I do have very crude versions of a dns and dhcp server but they're not ready for release really. I might offer them to the US developers for future releases so make the virtual host setup workable out of the box for users.

Older versions of US didn't need a compiler like lazarus (good to see some popular software is still made in object pascal!). Instead php scripts were executed via a batch file - and IMO this is still the better way of doing it rather than a gui which is possibly limited to certain OS's and may require runtimes etc.

If you want to avoid this dependency problem you could use an older version of uniformserver - version 7 (orion) does not need any runtimes as apache was compiled with a different compiler. I still have no idea why they changed this but it pretty much killed portable wamp setups on usb drives overnight. Use the older 7x servies of uniformserver and you'll be able to run it via usb as normal. It's also very flexible if you want to hack it up and add features.

Did you restart apache? Also no you don't have to use a ssl folder - you can use www if that works for you. Some websites prefer to have a non ssl section and then a seperate ssl section (eg a login page) for whatever crazy reason so a lot of server setups try to offer this so the user has a choice Also you don't have to use mysite.localhost... you can just use .lan instead which is quicker and easier (or you could just use one letter instead if you really wanted!). Talking of which, have you added mysite.localhost to your hosts file so that your dns lookups don't fail?

It won't be US at fault it'll be apache if anything.. so no point moaning about the uniform server project.. What i'd do is delete each line of the virtual host config until you find the one causing the problem. At that point you can then diagnose whats going wrong. I've had similar faults to yours - including apache not starting cos it can't access log files... total pain in the grass but you just have to keep at it. I had to delete 15 virtual host configs from my http.conf until i found the fault - good job CTRL Z works well in notepad++ lol

Note sure about the latest version of US (I'jm still using 7.0.1 orion - it's brilliant and means no runtime dependencies) but in my version there is a tool for creating ssl certificates located in \UniServer\unicon\key_cert_gen\Run.bat It only creates a cert for the main server (not virtual hosts) but it's hackable.. As for seeing the vhosts you need to change teh ssl config file - it's similar to http.conf.

Not sure.. i'm still using orion 7.0.1 lol and think that might well be 32bit as it used to run on my old 32bit machines...

localhost should open the local site. I have a hunch your DNS might be a bit borked.. ONLY the localhost address should work for you though - it's set in the hosts file of your PC so the name localhost translates to 127.0.0.1 - or should do unless it's been removed from your hosts file. IF it has been removed then your browser will try adding extensions to the address - so for localhost it will try localhost.com then localhost.net then localhost.org (that was the order IE used to do it in - not sure about newer modern browsers but they do typically start with .com). So you have two choices - either edit your hosts file on your PC or get yourself a local dns nameserver to run on your PC and then change your windows dns settings to use that and then configure that server with your loopback or local network address for all the domains you want to host locally. Note that if you're hosting them on your PC they don't have to be registered anywhere - eg i use home.lan for one of my local domains - it's setup in my nameserver and apache - and that's it, the browsers looks it up via the nameserver and then connects to apache. It's quite simple really but because normal internet domains work all over the web and are hosted on the most powerful dns nameservers available there's money in it. Note though that you can't setup your own domain registrar - you'd need the top level nameservers to recognise your server and they won't do that!

Hi Sorry this reply is a few years late lol.. In Orion (uniserver 7.x range) if you go into uniserver\unicon\main\includes\config.inc.php scroll to the bottom and there are these two lines: For Apache change S1 to 2.2 so it looks like this: If apache is installed already then uninstall it - then reinstall it using the install script. You'll now find that "Apache.exe -k restart" works well. Unfortunately the multiple servers feature of uniformserver won't work as intended anymore - but i've never used that anyway and never really understood it's purpose when you have virtual hosts - which this feature is needed for when creating them on the fly.. Twinky