I'm trying to set up a virtual host on OpenLiteSpeed 1.4.39. I've followed the official guide, but OpenLiteSpeed just won't acknowledge my domain name, hence my virtual host won't start.
I have however defined the desired domain name under Virtual Host > General > Domain Name
Under listeners and Virtual Host Mappings, I've connected my virtual host, listener and domain name.
But the virtual host will not start?
Does anyone have any ideas?
Thanks.
If you go to "Dashboard" , the "Server Error Log" section , do you see any related info there? it should state what's going on or why it fails.
Related
I have hosted my .Net project in IIS server and now I have the IP address.I want to change it to host name and I have already tried following steps
1) Add the Host Name in site bindings according to my existing IP address in IIS server
2) Do changes in host file(C:\Windows\System32\drivers\etc) according to the added host name
But I am getting following error when I navigate host name in browser
Bad Request - Invalid Hostname HTTP Error 400. The request hostname is
invalid.
What is the solution for this problem ??
Where did you host the IIS server? On-premise domain environment or Cloud VM with public firewall IP address?
If you are hosting the web server in domain environment, then you need to create a CNAME for your web server in DNS and set binding host header for your website in IIS.
If you are just hosting the web server in cloud VM, then you should purchase a public domain from domain provider like Godaddy and map the domain name to your Virtual machine'S public firewall address. After that, you should add host name to your IIS site. Finally, you should be able to access the website. Just remember to allow port number in firewall inbound rule.
I have created a VM which has a server running at localhost:8675/ which I had wanted to connect to my host machine at the same port for ease of understanding. I was following these to documents for information:
https://www.virtualbox.org/manual/ch06.html
http://www.howtogeek.com/122641/how-to-forward-ports-to-a-virtual-machine-and-use-it-as-a-server/
When I was in my VMWare Workstation, I clicked on my VM, then did: Edit > Virtual Network Editor. After that, enabled Change Settings which relaunched the window in admin mode. I clicked on the Row with Type NAT and external Connection NAT and in the VMNet Information with the NAT radio button pressed, I clicked the NAT Settings Button.
I said: Add... and then did:
Host: 8675
Type: TCP
VMIP: 127.0.0.1:8675
Description: Port Foward of 8675 from Host to VM.
It looks like everything is good. I say Ok and Apply in succession. It looked like it shut down nat and restarted some services.
I confirmed in the VM, the 127.0.0.1:8675 is correct.
In the HOST, I tried to go to: http://localhost:8675/ and it says: ERR_CONNECTION_REFUSED
I figured this was all I needed to do.
I was looking up some additional information and noticed that some people have had to configure firewalls. I wasnt sure if i needed to though, as I was thinking that the HOST and VM are all in 1 actual machine, it might be entirely self contained.
Is there a critical task I am missing?
I saw this post: https://superuser.com/questions/571196/port-forwarding-to-a-vmware-workstation-virtual-machine
which told me to just adjust it to bridged and use it that way. Does this solve the issue of connecting HOST / VM Issue.
I don't want to say this is the correct answer though as the question itself is particular to NAT, but this is a valid alternative answer that does work.
This is solves the base issue at hand, but not the question.
When you use NAT, the host system and the guest boxes have completely different IP addresses on their virtual subnet, so my guess is that when from the host system you try to connect to localhost:8675 you are actually trying to connect to port 8675 of the host and not of the guest. So don't use the localhost or 127.0.0.1 syntax, but discover the real IP address of the guest and use it.
If your guest is Windows use the ipconfig command, if Linux use ifconfig.
Probably you will also have to configure the firewall on the guest side.
EDIT:
Commenting the sentence "NAT: Used to share the host's IP address.": it probably refers to the IP address of the real ethernet adapter you have on your host and that is shared by host and guests to access the internet. That's not related to the way your host and guests communicate together. For example I use VMware Workstation to run a virtual Linux box in Windows. Selecting NAT, VMware creates a virtual subnet called VMnet8. In this subnet the virtual router has address 192.168.120.0, my Windows host is assigned a virtual ethernet adapter with address 192.168.120.1 and my Linux guest has got address 192.168.120.128. So when I want to access a Samba shared folder from Windows I type "net use * \192.168.120.128" in a Windows command prompt. When I want to access a Windows shared folder from Linux I type "sudo mount.cifs //192.168.120.1/path_to_shared_folder target_folder".
I believe you actually answered your question correctly as I was following it and achieved desired outcome.
IMHO, the error: ERR_CONNECTION_REFUSED indicates that a firewall on your host OS or guest OS (your VM) or on both doesn't allow the communication through the given ports.
The easiest thing would be to try to disable firewalls on boths, your HOST and GUEST OS.
Not sure what are your OSes, but here is just a good guide for setting up firewall rules on Ubuntu
I have question that when I start org.jacorb.naming.NameServer on my machine. It gives me an IOR.
My machine had 2 IP's:
Private like 192.168.64.39
Public like 209.153.66.13 (machine-abc.mynetw.com)
When I try to connect and register to Naming context. I get and error that
retries exceeded.. can not connect to 192.168.64.39:2508
I decoded the IOR URI and found that it points to my private IP over LAN. So When I try to connect to it I get given exception. What shall I do So that on decode I get Public IP or HOST name.
So that I can access it remotely.
Thanks
Use, -DOAIAddr=<Machine name IP>
where <Machine name IP> can be host name or IP Address.
But Jacorb 2.3.1 has bug if we write Host name then not necessarily IOR will resolve to HOST name it will consist of IP address only.
I have a deployed my web app in tomcat and is working fine on localhost. But when i try to access it from virtual box (windows) it returns "Requested resource not found"
from localhost the url is -
localhost:8080/finance/entries
works fine
from virtual box url becomes -
localhost:8080/finance/null
Any idea whats causing this?
I have firewall turned off.
localhost is "the machine I'm running on". On VirtualBox it's the operating system that you run within this virtual machine itself. You'll have to find out an actual IP address for your "host" operating system, e.g. use "ipconfig" or "ifconfig" (one of them should work on whatever OS you're running) and choose one of the IP addresses that are printed.
So: Get the IP address of your "host", then enter it on your "guest". Assuming you'll find an IP of 10.0.0.1, you'd access 10.0.0.1:8080/finance/entries from your guest operating system (this address will work on your host as well). Only localhost is special, because every system knows how to resolve that - it's "me", and virtual machines introduce quite a bit of split personality for your computer
When I up some app on my machine at localhost:3000/somecontroller. Is possible to turn public to world if I try mymachineip:3000/somecontroller ? Sorry if is a dumb question...
Rails apps default to listen on 0.0.0.0:3000, which really just means "listen on all interfaces, on port 3000". So yes, you should be able to access it from another machine via its IP address. (If you run a firewall or anything on your machine, though, you may need to open up the port).
You have to configure the firewall to allow access to your machine. Your router has a public IP. You can figure the public IP out, if you go to http://whatismyipaddress.com/, or so similar site.
Then you can configure your firewall to allow access to your machine. Open your router settings, and open a port to your local machine IP.
http://www.wikihow.com/Set-up-Port-Forwarding-on-a-Router
It's also a good idea to give the machine a static IP, bc the IP can change when the machine restarts.