I'm trying create a simple web server inside Azure using SQLite as a database and PHP with Apache as a backend. I was able to create a VM in the new portal, access it with SSH, git clone the software inside it, and add an Inbound security rule to port 80. Still my application is not accessible on my browser. Is there any other configuration I am missing?
Here are the steps I did on azure portal:
Virtual Machines -> Add -> Chose ubuntu server 14.04, and deployment model "Resource Manager", clicked on Create.
Filled in a name, username to connect to the vm, password authentication, created a new resource group, and the location closer to me (Brazil South).
Selected "A0 Basic" size
On settings I clicked on "network security group", and added a new rule for port 80, with priority 1010.
Finally on summary I clicked OK and waited for about 4-5 min to the console show me an OK message.
After that I log into the VM with ssh, ran sudo apt-get update followed by sudo apt-get install apache2.
When I type the public IP of the VM in the browser, it just keeps loading forever but doesn't show anything. Neither and error, nor the apache default page.
Related
i get this error for installation script that worked perfect on EC2 vm but now seems that i can't reach the site , should i add some inbound rule or something to enable apache2 server ? the error in the chrome is
This site can’t be reached *.*.*.*.com’s server IP address could not be found.
Try running Windows Network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN
Network Security Group
Azure VMs do not have any ports open firewall ports by default unless you open them when you provision your VM. When you created your Azure VM in the Azure Portal, you likely created a Network Security Group for the VM. If you didn't specify any ports to open during the VM's creation, you'll need to open up the VM's firewall.
To Open Ports
To open up the ports on the firewall, head out to the Azure Portal (where you set up the VM). Find the VM in the list of resources. It should take you to a page for your VM where the name, status, location, size, IP address, etc will be displayed. On the left side, you'll have a vertical menu > Select Networking. From there, you'll be able to see currently active firewall rules for the VM. Since you're likely missing HTTP (80) and HTTPS, select add inbound port rule. From the dropdown for service, select HTTP and assign a name/priority. Perform the same options, except this time selecting HTTPS (443). Press save and test. You should be able to access Apache running on the VM.
Additional Troubleshooting
The script you used may have inadvertently set up the VM's iptables. You can view Linux's firewall with sudo iptables -L to verify that no firewall rules have been enabled. Since Azure handles the firewall, you shouldn't need any iptables rules, but they could always be added for additional security.
This answer assumes that you do not have Azure's Load Balancing servers installed in front of the VM.
I have successfully installed Apache Guacamole on my DigitalOcean VPS.
Now I need to create a new connection to my windows 10 pc.
I cannot get that to work.
I am very confused what settings I need to fill in to connect to the pc.
Here are screenshots of the settings I can fill in. I am going to use RDP and am unsure how to find the domain, host, etc of my pc. Maybe there is other settings I need to fill in too?
Please help as I have been trying for weeks. Thank You.
New Connection Settings Picture
New Connection Settings Picture
First, make sure that both tomcat and guacd services are running. Usually, both are installed on the same machine.
On the settings page, select RDP as the protocol (in the images you have posted, VNC is selected). Next, in the "Parameters" section, enter hostname ip and RDP port (3389 is the default). If guacd is on the same host as tomcat, there is no need to enter anything in the "Guacamole proxy parameter" section.
The settings page is a bit different when RDP is selected, but you should also populate windows username, password and domain of the remote PC where you want to connect. The parameters are the same as the one you are normally using to logon to this PC.
Also, make sure that the remote windows 10 PC is accessible from the DigitalOcean VPS. You may test this by logging to the VPS machine and issue the following in the terminal
telnet <remote windows pc ip> 3389
If you can connect with telnet, this means that remote PC RDP server is accessible; otherwise, you have to check for network related issues (firewall, different lans...).
If everything above is ok, then please post the tomcat log (catalina.out) and guacd log (usually in /var/log/syslog).
Referring to below link Installed Hortonworks Sandbox on Oracle VM Virtual box.
https://hortonworks.com/tutorial/learning-the-ropes-of-the-hortonworks-sandbox
After starting the VM , Connected to host IP on port 2222 using Putty as user root. Changed Admin password successfully. Checked the status of Ambari Server and found in started state.
loaded the Splash page successfully on the URL http://sandbox-hdp.hortonworks.com:8888
Now While loading Dashboard on URL http://sandbox-hdp.hortonworks.com:8080/main/dashboard/metrics , Authorization popup not accepting Any of the UserId/Password combinations provided on HortornWorks website(link provided earlier)
I tried with admin/"My Password" and maria_dev/maria_dev and raj_ops/raj_ops. Authorization getting failed for every set of userid/pwd.
I have checked the port forwarding is enabled for port 8080 on VM Machine. Any further pointers appreciated.
Installed on VMWare instead of VirtualBox and It worked. Was able to launch and login to Ambari.
Can someone help me to write script to perform below steps in weblogic.
1.Stop Managed Servers
2.Stop Node Manager
3.Stop Admin Server
4.Delete the tmp,cache folders.
The steps you mentioned can be done with WLST and Node Manager. However, you need to make the following adjustments:
Configure Node Manager/WebLogic Domain to stop using the demo SSL certificate when accessing/starting Node Manager.
Configure Node Manager
Edit nodemanager.properties and set the following:
SecureListener to false
QuitEnabled to true
Restart Node Manager
Configure WebLogic Domain
Login to WebLogic Domain
Under Environment, Machines: click the Machine name configured
Under Configuration, Node Manager: set Type to Plain and save
Restart WebLogic Domain (Admin Server + Managed Servers)
Configure WebLogic Domain's Node Manager Credentials. The default is usually the username/password you entered when creating the WebLogic Domain. However, it is also a good idea to set different credentials for the Node Manager. This is totally optional, especially when working in a development environment.
Login to WebLogic Domain
Under Domain Structure, click the Weblogic Domain name
Under Security, General: click Advanced
Set the NodeManager Username and NodeManager Password/Confirm NodeManager Password and click Save
For this answer, I will use nodemanager/nodemanager_pwd as sample values.
Assuming you have one Admin Server and one Managed Server, both on the same machine, write the following commands in a Python script:
# Connect to the Node Manager running on localhost with port 5556.
# Change the DOMAIN_NAME and the DOMAIN_HOME as appropriate
nmConnect('nodemanager','nodemanager_pwd','localhost','5556','DOMAIN_NAME','DOMAIN_HOME','PLAIN')
# Start the Admin Server.
# The following command assumes that the
# name of the Admin Server is AdminServer
nmServerStart('AdminServer')
# Start the Managed Server. Again, change the Managed Server name as appropriate
nmServerStart('Managed_Server_01')
To stop the Managed Server and Admin Server, it's the opposite direction with the sequence, and now you need to use the nmKill command. The stopNodeManager() is possible if the QuitEnabled property was set to true in the nodemanager.properties file.
nmConnect('nodemanager','nodemanager_pwd','localhost','5556','DOMAIN_NAME','DOMAIN_HOME','PLAIN')
nmKill('Managed_Server_01')
nmKill('AdminServer')
stopNodeManager()
When invoking the Python script that contains the commands above, execute the following command:
$MW_HOME/oracle_common/common/bin/wlst.sh startup.py
$MW_HOME/oracle_common/common/bin/wlst.sh shutdown.py
As for the clearing of the tmp/cache folders, these can all be done via shell script (assuming you're running on Linux)
I've created literally dozens and dozens of web servers in my day, but this is my first attempt with Windows Azure and I'm running into some problems. I just started migrating from AWS recently.
First of all, I'm running Ubuntu 13.04. Firewall disabled (for debugging), Apache2 installed correctly (using apt). SSH works fine as do many other services with both the DNS hostname and public IP. Virtual host is set up correctly and validated. However, I cannot access the HTTP website either through the Azure provided subdomain or the virtual IP. It just times out.
This is also my first time using Ubuntu 13.04 as well. So, through the powers of deduction, I'm assuming there is something I'm missing either with this new version of Ubuntu or some quirk in Azure. Does anyone have any suggestions?
SOLUTION
These steps to create "endpoint" works fine for all VPS:
open "virtual machine > endpoint > add endpoint"
choose "next"
set "name:http, protocol:tcp, public port:80, private port:80"
choose "complete"
and then must wait for activation and then for some time.
If you are using Azure Resource Groups along with your VMs (which is available on the new portal) you cannot use endpoints because it's not available there, so you should follow the following to open up the HTTP port or ANY other port:
1- Select the VM that you want to manage ports on.
2- In settings, click on Network Interfaces and select your network.
3- Go to Network Security Group and select your group.
4- Add Inbound or Outbound security rules depending on what you need.