The scenario:
You're behind a proxy server on Windows. You've configured TortoiseHg to use a proxy server; that is you've entered a server name/IP and port number. You are able to connect to the internet using Internet Explorer. But when you try to pull or push and it produces the error message "SSL error: unknown protocol".
(I plan to answer this myself.)
The cause is that Internet Explorer is using an automatic proxy configuration script and TortoiseHg is using a particular proxy server. IE is not using the same proxy server because the automatic script picked a different proxy server.
The solution is to enter the proxy server used by TortoiseHg in IE's connection settings, or figure out which proxy server you're using at the moment and tell TortoiseHg to use that one. You may need to browse an external web site before TortoiseHg can connect.
You can figure out which proxy server you're using by browsing with IE and then running the DOS command:
netstat
and you'll see some connections in the Foreign Address column on port 80 or 8080 (common proxy server ports).
In addition to your excellent tip, I offer one more...
If your company is using an automatic proxy script, then the proxy used for web browsing may not be the one you need for Mercurial. Thus if you try the proxy you find via netstat, and you get "getaddrinfo failed" errors in tortoise, then try this...
Get the proxy script address: IE->config->Internet Options->Connection->LAN ?Settings. Copy the url from the "Address" box.
Browse to that address and save the file to disk.
Open that file in notepad and scroll to the end, it probably ends with something like-- return "PROXY ipaddresshere:port" that's the IP and port you need.
Plug that IP and port into tortoise: right-click the repo, click settings, click proxy, put the ip and port into the Host field. I generally don't need user and password so try without it first.
Related
Apologies if this is a bit basic:
I have a Google Compute Instance running Windows Server 2012 R2. It has a valid admin account and password (checked via gcloud). The external IP address can be pinged, the system has been stopped and started successfully. The gcloud commands execute successfully etc etc.
If I try to RDT in I get the unsuccessful message. If I use the RDT (Chrome) option in the Google Cloud Platform admin page I get this message:
In order to use the Chrome RDP Extension, you must configure VM
instance so that it has an external IP address, username and password.
Note: You must configure the network firewall to open TCP port 3389 to
enable RDP access.
Note that ALL of the above are correct and confirmed.
I am sort of going round in circles, I've tried to use powershell on a windows system to RDT in to no avail. Again, using the built in Bash serial access I can get to the system and, for example, retrieve the admin account and password, BUT RDT FAILS.
I have tried using the powershell command Enter-PSSEssion... and I initially got a winrm error, apparently the IP address needs to be in trustedhosts. Fixed that and now I am getting a message that I need to verify that winrm is running on the destination computer, catch 22, that's why I'm using winrm, to access the destination computer.
Any ideas what I might try next?
Thanks.....
create a rdp network tag for firewall rule, which allows tcp:3389 ingress and and then apply it to the instance in question... someone (assuming you're at work) might have removed/edited these rules trough the console or gcloud command.
I've setup an vsftpd on my Ubuntu 16.04 using this tutorial.
I can connect to server using FileZilla but not through PhpStorm. It issues this error when I try to upload a file to server:
Failed to transfer file 'C:\xampp\htdocs\sherkat\artisan.php': cant open output connection for file "ftps://SERVER-IP/artisan.php". Reason: "500 Illegal PORT command.".
What's wrong with my config?
The FTP protocol supports two modes for the data connection. In the traditional mode, called "active" (which is the default), on each command sent by the client the server creates a connection back to the client and uses it to send the response. This is impossible on the most setups nowadays (actually, in the past 20+ years) because of firewalls.
There is another mode, called "passive", where the data connection for the response is also initiated by the client. It works through firewalls without problems.
Press the "Advanced options..." button, check the "Passive mode" option and you're good to go!
As a side note, a better way is to use the SFTP protocol. If you can connect through SSH to your Ubuntu box, most probably you can also use SFTP to transfer files to it, without any other setup. FTP is an old and convoluted protocol. SFTP uses a secure connection (maybe it's not that important for you), and a simpler protocol.
I just installed Couchbase Server 3.0.2 on Windows 8.1. The Installation went through successfully but I am unable to access http://localhost:8091/index.html.
"Google Chrome's connection attempt to localhost was rejected. The website may be down or your network may not be properly configured."
I tried to check if anything listening on that port using the command.
netstat -an -p tcp
But found nothing is listening on that port and the closest port i found was 8092, so thought may port has changed so when i try to browse on that port i got a json response as below.
{"code":404,"status":"fail","message":"controller_not_provided","ResultDate":"2015-02-06T17:13:23.2551859Z","Progress":-1,"Result":"No controller provided."}
please check the couchbase service form the windows control panel. sometimes it will not start the service automatically ,it may be manual. start the service manually , if not started then check the localhost url.
you can also start the service form the desktop icon. double click on the couchbase icon it will start the service automatically and it will open the url in your default browser.
if still facing the problem not able to start the couchbase server , follow the
.link
it describe each and every steps of the couch base installation process.
Nitrous Desktop fails to sync with "Error: connection failed". Even after restart, delete and generate new SSH keys. I moved everything at ~/workspace but it stills says the same. Any ideas?
If you are using Windows then you will want to ensure that the nitrous-ssh app is not being blocked by your Windows firewall. You should have been prompted about this when first enabling File Sync, but if you did not check these boxes when first connecting then you will want to locate it within your firewall settings and allow it on all networks.
You may also want to check that the port which Nitrous Desktop uses is not being blocked by your network. The port can be found within the SSH URI field on the boxes page:
https://www.nitrous.io/app#/boxes
The port # is at the end of the SSH URI.
I am trying to get the MAC client app to sync files and enable port forwarding.
When I turn on port forwarding I get "Port Forwarding Error: Authentication failed."
When I turn on File Sync I get "File Sync Error: Lost connection with the server"
I can see my boxes in the client app and tell when they are running or not.
Any help with this issue would be appreciated.
Worked with NitrousIO tech support and it was an issue with ssh keys. They had to delete my keys on their end and register them again.
If this happens to you, you will want to contact support.