I'm just starting out with intern/saucelabs. Whenever I try a remote test, I'm getting Error: failed to connect to tunnel VM.
My intern.js has
environments: [
{ browserName: 'firefox', version: '28'},
],
tunnel: 'SauceLabsTunnel',
tunnelOptions: {
username: 'foo',
accessKey: 'xxxxxxxxxxxx-xxxx-xxxx-xxxx-xxxx'
},
Execution log
$ intern-runner config=theintern/intern-sauce.js
Listening on 0.0.0.0:9000
Starting tunnel...
Using no proxy for connecting to Sauce Labs REST API.
**********************************************************
A newer version of Sauce Connect (build 1283) is available!
Download it here:
https://saucelabs.com/downloads/sc-4.3-linux.tar.gz
**********************************************************
Started scproxy on port 44275.
Starting secure remote tunnel VM...
Secure remote tunnel VM provisioned.
Tunnel ID: 6586b9012ca2424b8ecd6bd6970e996c
Secure remote tunnel VM is now: booting
Secure remote tunnel VM is now: running
Remote tunnel host is: maki76026.miso.saucelabs.com
Using no proxy for connecting to tunnel VM.
Establishing secure TLS connection to tunnel...
Cleaning up.
Finished! Deleting tunnel.
Error: failed to connect to tunnel VM.
Error: failed to connect to tunnel VM.
at reject <../../../../../../../usr/lib/node_modules/intern/node_modules/digdug/SauceLabsTunnel.js:353:17>
at readStartupMessage <../../../../../../../usr/lib/node_modules/intern/node_modules/digdug/SauceLabsTunnel.js:381:12>
at <../../../../../../../usr/lib/node_modules/intern/node_modules/digdug/SauceLabsTunnel.js:434:12>
at Array.some <native>
at Socket.<anonymous> <../../../../../../../usr/lib/node_modules/intern/node_modules/digdug/SauceLabsTunnel.js:428:21>
at Socket.EventEmitter.emit <events.js:117:20>
at Socket.<anonymous> <_stream_readable.js:746:14>
at Socket.EventEmitter.emit <events.js:92:17>
at emitReadable_ <_stream_readable.js:408:10>
at emitReadable <_stream_readable.js:404:5>
In case it's significant, I'm currently on the free tier.
Some of the most common issues folks run into with Sauce Connect are related to firewall and proxy settings. Please ensure that 443 is open between Sauce Connect and *.saucelabs.com. If a proxy server is used to route traffic on your network Sauce Connect supports proxy servers by passing the --pac or –p flag.
Please download the latest version of Sauce Connect from https://docs.saucelabs.com/reference/sauce-connect/ and start the client with all the necessary flags (a full list is available on the aforementioned page). If this version does not work please start Sauce Connect passing the -v flag, this will generate a verbose log file which will help Sauce Labs diagnose connectivity issues.
Related
Hello i like to change to VSCodium with linux but i have a problem, in VSCODE i use remote-ssh and works fine, but this same package in VSCodium doesn't work.
It ask me password and after i have a error:
[20:38:29.280] SSH Resolver called for "ssh-remote+1.1.1.1", attempt 5, (Reconnection)
[20:38:29.281] SSH Resolver called for host: 1.1.1.1
[20:38:29.282] Setting up SSH remote "1.1.1.1"
[20:38:29.283] Acquiring local install lock: /var/folders/bz/gzbhhfv928n_jdqsk23ttycm0000gn/T/vscode-remote-ssh-eb13906b-install.lock
[20:38:29.283] Looking for existing server data file at /Users/XXXXXXXXXX/Library/Application Support/VSCodium/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-eb13906b-cea9d1a4b17966719d8c5f3cdd914480f7cec47c-0.87.2022090715/data.json
[20:38:29.284] Using commit id "cea9d1a4b17966719d8c5f3cdd914480f7cec47c" and quality "stable" for server
[20:38:29.286] Install and start server if needed
[20:38:29.291] askpass server listening on /var/folders/bz/gzbhhfv928n_jdqsk23ttycm0000gn/T/vscode-ssh-askpass-da57138f4d7832fc3734ad7a50dc225ccbef89e5.sock
[20:38:29.291] Spawning local server with {"serverId":5,"ipcHandlePath":"/var/folders/bz/gzbhhfv928n_jdqsk23ttycm0000gn/T/vscode-ssh-askpass-de457e3bd9a608cfdd3faf37d5903491af5d4969.sock","sshCommand":"ssh","sshArgs":["-v","-T","-D","52249","-o","ConnectTimeout=15","1.1.1.1"],"serverDataFolderName":".vscodium-server","dataFilePath":"/Users/XXXXXXXXXX/Library/Application Support/VSCodium/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-eb13906b-cea9d1a4b17966719d8c5f3cdd914480f7cec47c-0.87.2022090715/data.json"}
[20:38:29.291] Local server env: {"SSH_AUTH_SOCK":"/private/tmp/com.apple.launchd.DkNdtZMLnV/Listeners","SHELL":"/bin/zsh","DISPLAY":"1","ELECTRON_RUN_AS_NODE":"1","SSH_ASKPASS":"/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/local-server/askpass.sh","VSCODE_SSH_ASKPASS_NODE":"/Applications/VSCodium.app/Contents/Frameworks/VSCodium Helper.app/Contents/MacOS/VSCodium Helper","VSCODE_SSH_ASKPASS_EXTRA_ARGS":"--ms-enable-electron-run-as-node","VSCODE_SSH_ASKPASS_MAIN":"/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/askpass-main.js","VSCODE_SSH_ASKPASS_HANDLE":"/var/folders/bz/gzbhhfv928n_jdqsk23ttycm0000gn/T/vscode-ssh-askpass-da57138f4d7832fc3734ad7a50dc225ccbef89e5.sock"}
[20:38:29.292] Spawned 11544
[20:38:29.437] > local-server-5> Spawned ssh, pid=11548
[20:38:29.440] stderr> OpenSSH_8.6p1, LibreSSL 3.3.6
[20:38:29.490] stderr> ssh: connect to host 1.1.1.1 port 22: Connection refused
[20:38:29.492] > local-server-5> ssh child died, shutting down
[20:38:29.496] Local server exit: 0
[20:38:29.497] Received install output: local-server-5> Spawned ssh, pid=11548
OpenSSH_8.6p1, LibreSSL 3.3.6
ssh: connect to host 1.1.1.1 port 22: Connection refused
local-server-5> ssh child died, shutting down
[20:38:29.497] Failed to parse remote port from server output
[20:38:29.497] Resolver error: Error:
at g.Create (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:583821)
at t.handleInstallOutput (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:582473)
at Object.e [as tryInstallWithLocalServer] (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:622972)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
at async /Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:642100
at async t.withShowDetailsEvent (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:645820)
at async /Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:621444
at async T (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:617950)
at async t.resolveWithLocalServer (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:621059)
at async t.resolve (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:643428)
at async /Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:722225
[20:38:29.499] ------
Microsoft's remote extensions won't work with VSCodium because Microsoft restricted them to only work in VS Code. Their licenses also don't permit any usage in any editor other than Visual Studio family products. More context: https://news.ycombinator.com/item?id=31714082
I followed the instructions listed here, https://docs.mongodb.com/manual/tutorial/install-mongodb-enterprise-on-red-hat/, and tried to install on a remote server from my local machine. I ssh from my local machine into the server and performed the steps for installation.
I'm not sure if there are additional steps that need to be completed or whether you have to set Directory Paths that are not the default ones since you are using a server instead of local machine. My current error is when I run mongo from my terminal and I get this error
Error: couldn't connect to server 127.0.0.1:27017, connection attempt failed: SocketException: Error connecting to 127.0.0.1:27017 :: caused by :: Connection refused :
connect#src/mongo/shell/mongo.js:374:17
#(connect):2:6
exception: connect failed
exiting with code 1
[h699972#csc2cxp00020938 ~]$ mongo --host
sudo vim /etc/mongod.conf and setting bindIp: 0.0.0.0 did not work. Any help would be appreciated.
I try to implement Passport-azure-ad OIDCStrategy on my node application.
It is working find in my personal computer but with my corporate laptop (without VPN or proxy configured) I cannot connect and I get that error :
authentication failed due to: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND 3128
I don't understand why because I can access by a browser to https://login.microsoftonline.com/ without any issues.
I don't understand what endpoint node try to contact and why the tunnel socket cannot be established.
Any help ?
Thanks
Installed DSE on CentOS7 and saw no errors, I'm able to connect to cqlsh from the local machine and and I'm able to also do a telnet on the port.
However the problem is that when the same is done from a remote machine I get the below error
cqlsh XX.XXX.XX.XX 3389
Connection error: ('Unable to connect to any servers', {'10.223.61.49': ConnectionShutdown('Connection to 10.223.61.49 was closed',)})
To check the connectivity I did a telnet on this and see the below error
telnet XX.XXX.XX.XX 3389
Invalid or unsupported protocol version (13); supported versions are (3/v3, 4/v4, 5/v5-beta, 65/dse-v1)
I tried updating the Python version, also few tweaks to change the py script also didn't help
I am new here.
Few days ago, attended MS azure events, and today registered with Azure (free account).
VM Environment: VM = CentOS 7, apache+php+mysql+vsftpd+phpMyAdmin
everything is up and running, able to visit the "info.php" via its public IP address.
SeLinux = disabled, Firewalld disabled.
my problem is not able to connect this server via Filezilla (PC client).
from Windows command prompt (FTP/put) is working, able to upload files.
But via Filezilla
Status: Connecting to 5x.1xx.1xx.7x:21...
Status: Connection established, waiting for welcome message...
Status: Insecure server, it does not support FTP over TLS.
Status: Logged in
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/home/ftpuser"
Command: TYPE I
Response: 200 Switching to Binary mode.
Command: PORT 192,168,1,183,234,99
Response: 200 PORT command successful. Consider using PASV.
Command: LIST
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Status: Disconnected from server
Status: Connecting to 5x.1xx.1xx.7x:21...
Status: Connection established, waiting for welcome message...
Status: Insecure server, it does not support FTP over TLS.
Status: Logged in
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/home/ftpuser"
Command: TYPE I
Response: 200 Switching to Binary mode.
Command: PORT 192,168,1,183,234,137
Response: 200 PORT command successful. Consider using PASV.
Command: LIST
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
I believe that is because of the Network Security group settings for inbound and outbound rules, need open some port, but not sure, because I tried open 1024-65535 all allow, still not working.
If you use passive mode FTP, you should open ports 20,21 and ports that you need on Azure NSG(Inbound rules). You could check /etc/vsftpd.conf
pasv_enable=YES
pasv_min_port=60001
pasv_max_port=60005
For this example, you should open ports 60001-60005 on Azure NSG(Inbound rules).