Enthought Canopy on OSX "Could not connect to authentication server" - macos

After what seemed like a successful renewing of an academic license of Enthought Canopy 1.4.0 installed on OS10.9.2 executing any code would immediately return a crash report that said among other things:
User not logged in: Authentication failed: Authentication error: UNAUTHORIZED.
I did a complete clean re-install and now code runs but starting package manager returns an error:
Could not connect to authentication server. Reason: UNAUTHORIZED
Could not connect to Canopy server.
Please check your network connection.
Package manager will not be able to update or install new packages.
If you are behind a proxy firewall, please check your proxy settings in the Preferences dialog
My network connection seems to be fine and I have moved to another location to get on a completely different network and get the same result and am not aware of any proxy firewall on either network.

Related

Web deploy failing, says DESTINATION NOT REACHABLE

I honestly don't know where to start apart from mentioning I've tried absolutely everything and I feel like banging my head against the wall!
I've configured my IIS according to the Microsoft docs and also added Web Deploy 3.6.
In my services I have the following running:
In my windows firewall I have opened port 8172:
In my IIS I have enabled remote connections:
Within IIS I have a Site which points to an empty folder, when I right click -> Deploy -> Configure Web Deploy publishing I get this:
Using this, I've set up a publish profile in VS like so:
But get this error why I try and 'Validate' the connection:
Severity Code Description Project File Line Suppression State
Error Web deployment task failed. (Could not connect to the remote computer ("server2021"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.)
This error indicates that you cannot connect to the server. Make sure the service URL is correct, firewall and network settings on this computer and on the server computer are configured properly, and the appropriate services have been started on the server.
Error details:
Could not connect to the remote computer ("server2021"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.
Unable to connect to the remote server
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
I can't even remote to this server, I'm accessing it using TeamViewer.
I've viewed EventViewer logs on my local machine and it just says the same error which VS is spitting out.
I honestly don't know what I'm doing and I'd really really appreciate any help

Login to Xcode server stuck, "Unable to perform the request. CFNetwork error: An SSL error has occurred"

I am trying to setup a CI workflow, so created an Xcode server on my local machine, and am trying to create a bot, but cannot get past the login to the server dialog. It simply spins and spins, but errors out.
I started off by setting up an Xcode server on my local machine.
I try to add a login to the server:
But get stuck here (login is masked in the picture):
And if I wait long enough, I get this error message:
I am using Little Snitch and a VPN, but wouldn't this be trying to connect to the local machine and not using the network?

Forbidden access to socket message when running Python 2.7 web service locally on Windows 10

I have a Python 2.7 web service which uses Pyramid libraries. The service works fine on Linux machines, but when run locally on Windows 10 I get the following error when making post requests: "error: [Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions"
I can make get requests via a browser with no problems. Only post requests via an application seem to result in this error message.
I have tried turning off both Kaspersky anti-virus and the Windows firewall, but I keep getting the same error.
A possible reason could be that the current user account lacks sufficient permissions to bind to the port you have provided (port 80?). Try with a higher port(>6000 or something)
You can specify this configuration in your .ini file under the [server:main] section
For instance,
[server:main]
use = egg:waitress#main
host = 127.0.0.1
port = 6543

Web Test Fails With SocketException

I have recorded a simple web test in VS 2013 Ultimate and im attempting to run it on a remote agent.
I get the following error:
Request failed: No connection could be made because the target machine actively refused it 127.0.0.1:23109
If i change my run settings to only run the test locally it succeeds.
When i view the "Manage Test Controller" dialog the agents are registered and in the ready state.
I have checked the Controller and agent LAN settings and none of them is configured (or required) to use a proxy.
Does anyone have any idea whats going on?
So the problem was the Internet Explorer security settings on the agents and also Internet explorer was configured to use a proxy on the agents.
I logged onto the server and checked this initially but as my own user account. I then checked by logging on as the user the agents run as and removed the configured proxy from IE, lowered the security settings and all was well.

WebDeploy - just can't get it to work

I've installed Web Deploy 2.1 on a Server 2008 R2 running under VMWare.
In the IIS Manager (Management Service applet) I can see that "Enable Remote Connections" is checked and the port is set to 8172. Under "IIS Manager Permissions" I've added my Windows account (CORP\ekkis) and under the "Authentication" applet (for IIS) I have enabled "Windows Authentication".
I've also turned off the firewall.
So from the command line I test the system to work like this:
C:\Program Files\IIS\Microsoft Web Deploy V2>msdeploy -verb:dump -source:contentPath=\temp,wmsvc=192.168.0.70,username=CORP\ekkis,password=MyPass,authType=Basic -allowUntrusted=True
and get this:
Info: Using ID '9b954a0f-ff07-4e77-ba2c-d27472f5fda0' for connections to the rem
ote server.
Error Code: ERROR_USER_UNAUTHORIZED
More Information: Connected to the destination computer ("192.168.0.70") using t
he Web Management Service, but could not authorize. Make sure that you are using
the correct user name and password, that the site you are connecting to exists,
and that the credentials represent a user who has permissions to access the sit
e.
Error: Object of type 'contentPath' and path '\temp' cannot be created.
Error: The remote server returned an error: (401) Unauthorized.
Error count: 1.
I've also tried deploying with Visual Studio 2010 from the host OS with the following service urls (I haven't found proper documentation on how to form this url):
https://192.168.0.70/
https://192.168.0.70:8172/
https://192.168.0.70:8172/MsDeployAgentService/
https://192.168.0.70/MsDeployAgentService/
I've tried the non-secure versions as well but just cannot get it to work. What is the correct format for the url? and what permissions am I missing?
the errors from VS have varied depending on how I attempt it but below is a sample:
Could not complete the request to remote agent URL 'http://192.168.0.70:8172//MSDEPLOYAGENTSERVICE'.
The underlying connection was closed: An unexpected error occurred on a receive.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
Publish failed to deploy.
there really should be a guide out there to do this (yes, I've googled myself blue in the face)!
thanks - ekkis
ok, I've figured out that the correct url is:
https://192.168.0.70:8172/MsDeploy.axd
and that having the "Windows Authentication" enabled doesn't seem to make a difference. Also, having my account in the "Managers" list doesn't seem to make a difference either.
so the back end was all working fine (I've turned off the Web Deployment Agent Service). it was just the url I had wrong.

Resources