Unable to bind locally created project on default ports - moovweb sdk - windows

I am trying to create a new project locally in the moovweb developer dashboard using moovweb windows sdk. But the newly created project fails to start with below error:
listen tcp 0.0.0.0:443: bind: An attempt was made to access a socket in a way
forbidden by its access permissions.
Perhaps there's something already listening on port 443?
and same error for port 80.
Of course, there are other applications running on these two ports. So how do I change the default port that moovweb binds any local project to?
I looked their documentation, but couldn't find any relevant information regarding this (or may b I didn't look hard enough).
I am using moovweb sdk v6.3.10

If you are unable to temporary shutdown the applications that are using ports 80 and 443, then you should start the moovweb server using the -p and -ssl-port settings in order to start your server using a different port.
For more information you can type:
moov help server
into your terminal

Related

SonarQube on windows - can only view locally

I have a windows server 2016 machine which I have Jenkins running on. I wanted to install SonarQube. So have downloaded v7.1
I have managed to start sonarqube on the machine and can view the webserver at http://localhost:9000
I tried to view the page on a different machine using the IP address and port 9000, but this doesn't connect. Looking in the sonar.properties file I can see
Binding IP address. For servers with more than one IP address, this property specifies which
address will be used for listening on the specified ports.
By default, ports will be used on all IP addresses associated with the server. sonar.web.host=http://xx.xxx.xxxx.xxx
If I use http:// then sonarqube starts, but I can't see sonarqube from any other machine, if I don't use http:// (so just the ip) then it won't start with a bind error.
Has anyone experience of setting this up on windows?
Turns out it was something a lot simpler, the machine is being run on azure and there was no port 9000 endpoint

Enable Confluence to run on Port 80 in windows server 2012

I am having difficulty getting Confluence running on windows server 2012 on port 80. (the machine in hosted in Azure which is why I need to run it on port 80 (i dont have access to other ports from where I am trying to use this)).
I believe something must be running on port 80 , though i did a netstat -y and didnt see anything.
I think its IIS any idea how I should kill that or what else could be causing confluence to not run on port 80?
*confluence works find on say port 8090 but i need to run it on port 80.
mind you I cant get confluence to run on port 80 on the local instance of windows server, never mind accessing it from another location thus i dont think this has anything to do with azure
running a
netstat -abn
shows nothing running on port 80. Im still not sure why I cant get confluence to work locally on port 80.
A virtual machine in Azure is not directly public accessible. You need to configure endpoints in the cloudservice (which acts as a loadbalancer).
So for instance you can configure a public endpoint port 80 on the cloudservice to point to your VM port 8090. See http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-set-up-endpoints/ for more information.
If the Endpoint is open on Azure to the VM then my advice would be to check the firewall settings on the host. Typically most ports are shut unless they are explicitly opened by installing a feature like IIS (windows web server).

How to access Docker web app from host OS?

I've followed the tutorial on the docker.io website here:
http://docs.docker.io/en/latest/examples/python_web_app/
How would I access this app from a browser on my host OS?
Docker Remote API provides a way of accessing your Docker images and containers and performing many operations on them, through your Browser.
Here is the link for Docker API v1.6 Documentation
Hope it helps.
The tutorial explains how this works:
WEB_PORT=$(sudo docker port $WEB_WORKER 5000)
Look up the public-facing port which is NAT-ed. Find the private port used by the container and store it inside of the WEB_PORT variable.
# install curl if necessary, then ...
curl http://127.0.0.1:$WEB_PORT
Hello world!
Access the web app using curl. If everything worked as planned you should see the line “Hello world!” inside of your console.
Inside the container the application is listening on port 5000. This is translated automatically to an external port number accessible outside of the container. This makes sense because it allows multiple copies of your application to coexist on the same machine, each mapping port 5000 to a uniquely accessible port number for each app instance.
The documentation on port redirection has more details.

Cannot connect to named instance of SQL Server 2008R2

I am attempting to create a new Database Project in VS2010 via the New Project Wizard, and via this article: http://msdn.microsoft.com/en-us/library/aa833432(v=vs.100).aspx
I am on the 'Configure Build/Deploy' step, and am attempting to connect to a named instance of SQL Server 2008R2 that I just installed, called DEVELOPMENT. Assuming the server name is DB-01, I am using DB-01\DEVELOPMENT as the Server name in the dialog in the screenshot below. I'm also using the remaining settings in the dialog, but it keeps giving me the following error:
A network-related or instance-specific error occurred while
establishing a connection to the SQL Server. The server was not found
or was not accessible. Verify that the instance name is correct and
that SQL Server is configured to allow remote connections. (provider:
TCP Provider, error: 0 - A connection attempt failed because the
connected party did not properly respond after a period of time, or
established connection failed because connected host has failed to
respond.)
DEV is the name of a database I created on the DEVELOPMENT instance. If I use DB-01 as the server name, which is the default instance, it connects. In the past, we've been developing from a database on the default instance, with no issues, but I'm trying to move to local, source-controlled databases. What am I missing with this not connecting?
EDIT: As a little more context, it's not the username/pw combination, or the existence of the DEV db on the instance, because I receive different errors if either of those are incorrect. It's simply not able to connect once I give it the named instance.
Figured it out:
The default instance of SQL Server (called MSSQLSERVER in some places) uses port 1433 by default for incoming connections, which was opened in Windows Firewall. This is why I was able to connect to the default instance (DB-01). If you've created a named instance of SQL Server, by default these instances use port 1434 for incoming connections. These are TCP ports for each case. Well, I have to admit that I opened TCP port 1434 in Windows Firewall and still was not able to connect to the named instance remotely, and still am not sure why this was the case. So instead, I opened up a random port (6969) in Windows Firewall, and configured the DEVELOPMENT (named) instance to accept incoming connecting over that port only. For instructions on how to configure specific SQL Server instances to use ports other than the default, see this article:
Configure a Server to Listen on a Specific TCP Port
Once I configured the instance to use port 6969, I was able to connect with no issue. Hope this helps others that are having a similar/same issue.

Mac: How to see list of running network services?

I am writing an application that needs to connect with a running network service on a Mac.
Problem is, I have no idea what the service is called or even what port it uses. Is there a way to browse all running network services on my Mac?
More info:
I am connecting to a MIDI network session (found under 'Audio MIDI settings', present on all OSX installs). Am I correct in thinking this is a network service?
I am planning to use NSNetServiceBrowser to locate all local computers running this service. (is this the best way to go about it?)
Any help is much appreciated - thanks!
From:
"...no idea what the service is called or
even what port it uses..."
try in terminal:
nc 192.168.1.30 1-9999
Replace 192.168.1.30 by your ip, and replace 1-9999 to the port range you want to scan. 1-9999 would mean scan from port 1 to 9999.
2. From:
"...network services on my Mac..."
Try Bonjour Browser.
http://www.tildesoft.com/
Just a humble suggestion.
The Network Utility found under Applications/Utilities has an option to Port Scan a host, running against localhost will show you what ports are open for connections.

Resources