So i set up a rabbitmq server on my dev machine for a test.
I also set up the management portal and a user.
Everything works fine when on the windows server (iis).
I can browse to
https://server-name.rnd:15672/
and i can log in with the user
But i can't to do this remotely from anywhere else meaning i'm not even getting the log in page.
I tried
. opening the ports 15672 & 5672 (inbound and outbound rules)
but nothing...
What else can i do ?
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 had installed RabbitMQ on my windows machine long back. Now I want to access its management console web page. I tried the default ports 5672, 25672, 15672, 5671, 15671, 25671. Not able to access the page. I checked under windows 'services' and found it to be up & running.
How can I access the RabbitMQ Management console? How can I find on which port my rabbitMQ is running?
I am having some issues accessing the rabbitmq_management plugin.
I am running RabbitMQ 3.6.2, where rabbit is installed as a service and the plugin is enabled. Running on Windows Microsoft Server 2012.
Service runs fine, no errors in logs, however when i try and access the management tool via the web browser UI, "This page can't be displayed", I am sure i am going to the right port as the logs show the port it is running on, i have tried adding some rules to the Inbound on the firewall in case it was to do with ports and nothing seems to work. Any ideas?
EDIT
I am able to access the port via another machine on the network but does still not work in local host.
Yesterday I created an Azure Virtual Machine using the simple Win2008r2 + SQL2008r2 image.
I have deployed a website to the VM via an RDP session.
I am able to browse the website locally (via RDP) using
"http://localhost"
I understand that I need to add an Azure endpoint for port 80 to enable me to browse to the site from an external machine.
I have configured the Windows Firewall on the Azure VM to allow traffic on Port 80 inbound and outbound.
Could anyone please advise what I've missed or what I can do to troubleshoot?
---Update-----
I have learned a little more this morning. The website that I'm trying to host on the VM is an installation of Interwoven Teamsite v7.3.x. When I looked in IIS I could see that the "Default Web Site" was stopped. Another website called "TeamSiteSitePubPreview" had been created but was only bound to port 81.
So, what was presenting the website I could see when I browsed to
http://localhost locally?
I ran netstat -ano and this showed me that PID 1604 what listening on port 80. I then ran Process Explorer which told me that PID 1604 was allocated to "Appache HTTP Server".
I know nothing about About Appache, can anyone tell me if there's some Apache config that will be preventing connections from outside of the local server?
For reference, I just tested this sequence and it gives you a website accessible over the Internet:
Create a new Windows Azure virtual machine with the Windows Server 2008 R2 SP1 image.
Add an endpoint on public port 80, private port 80.
While the endpoint is being created, start setting the server up.
Remote Desktop in.
Add the Web Server (IIS) role with default settings.
Test the connection. You should get a HTTP 200 OK status.
If you want to troubleshoot your server, start checking for errors in the event log. Check also the website bindings in IIS (Port 80, IP Address *).
Also consider the connection issue might be on the client (your) side. For instance, DNS caching. Try connecting from another machine with direct Internet connection (such as another cloud server) or from a service such as isup.me.
Additionally, if all you want is to host websites in IIS, the Web Sites service has a more streamlined experience.
You will need to create an endpoint on port 80 thru Windows Azure Management portal as well. This endpoint opens a port in the Windows Azure Load-balancer.
Navigate to your VM within the portal and create a new Endpoint under the Endpoints screen of VM configuration within Azure management portal.
I am adding a new site on a server running other sites, some 'All Unassigned' (those that do not need an SSL) and the is the 4th site with a unique IP (these require an SSL). All other sites, including their SSLs (if applicable) are working.
When I ping the LAN IP from within the network, I get 'request timed out'. Pings to the other unique IPs get a response.
I've tried:
other unique LAN IPs
created a new website in IIS6
created a 'test' folder and pointed IIS there
Event Viewer logs for System or Application show no error messages.
I restarted IIS after each variation.
To my knowledge, pinging from within the network does not go thru my firewall, so I have not fooled with it.
an ASP.NET version issue would ping but throw a browser error, so I have not fooled with it.
Any thoughts on how to debug this issue?
Any suggestions welcome, and Thanks in advance.
Have you added the IP address to the network configuration on the Windows machine?
Ping doesn't have anything to do with your web server configuration or IIS.
To debug:
Make sure under Control Panel -> Network - > under TCP/IP Configuration that your server has the required IPs entered and that your subnet mask entries are correct.
Ping from the command line, so start - > run -> cmd
then at the prompt ping -ip address-
Make sure that your windows firewall is allowing ICMP packets in and out. If your network is protected from the internet by a separate firewall, you can turn the Windows firewall off to test.