I'm trying to connect my macOS (10.14.4) to L2TP server, but my Mac just pop up a window:
VPN Connection
Your connection failed because of an incorrect PPP setting. Verify your settings and try reconnecting.
photo
I have tried using my iphone to connect L2TP server and it worked perfectly (in the same local network).
Did anyone get the same issue before?
Delete your /etc/ppp/options and try to run this command.
sudo bash -c 'echo "plugin L2TP.ppp">>/etc/ppp/options'
Related
I have PyCharm Pro. I am trying to do remote development on a server. I have read the following Jetbrains tutorials:
Deploying Applications
Remote Development on Raspberry Pi
as well as the very helpful tutorial:
Remote debugging with pycharm the missing tutorial
While I seem to be able to set everything up, authentication fails when I try to connect to the remote server using the 'SFTP' protocol. I can make an SSH and SFTP connection from the CLI in a terminal so I know the ssh configuration settings are correct. However, in my case authentication requires ssh and having a Yubi key connected to my laptop. Does that make a difference?
Has anyone had a similar issue? If so, how did you resolve it?
On MacOS the challenge is where the IDE is getting it's ssh socket agent. To make this work in my case I have to launch the PyCharm Pro IDE from a terminal.
Go to '/Applications/PyCharm.app/Contents/MacOS' directory and launch with './pycharm'
Running expo bundler for react native in tunnel mode with expo start --tunnel only works the first time I run it after a fresh restart of my computer. Then, if for some reason I close the cmd prompt that is tracking expo and open another, running the same command gives this error:
Error starting tunnel could not connect to TCP port 5562: cannot connect to 127.0.0.1:5562: No connection could be made because the target machine actively refused it. (10061)
I think there has to be an easy way to resolve this since restarting works. Does anyone know where to start?
I've checked the following threads to no avail:
could not connect to tcp:5037: cannot connect to 127.0.0.1:5037: No connection could be made because the target machine actively refused it. (10061)
https://pisquare.osisoft.com/thread/42096-could-not-connect-to-nettcpwin-fvo35t9cv2q5457afserverservice-the-connection-attempt-lasted-for-a-time-span-of-0000020312902-tcp-error-code-10061-no-connection-could-be-made-because-the-target-machine-actively-refused-it-1921681691285457
I found a strange thing when using ssh -X to connect to two servers.
Ubuntu16.04 is installed on one server, while Ubuntu 18.04 is installed on the other. I upload a simple shell script as following to both servers:
#!/bin/bash
tab=" --tab"
options=()
cmds[1]="echo Banana"
cmds[2]="echo Cat"
for i in 1 2; do
options+=($tab -e "bash -c '${cmds[i]} ; bash'" )
done
gnome-terminal "${options[#]}"
exit 0
You know this script will open a new terminal window on server with two tabs. One tab will print "Banana", and the other tab will print "Cat".
Then I using ssh -X to remotely login into the first server (Ubuntu 16.04) and execute this script on server, I got a new terminal opened with two tabs on my pc. That is I saw the remote terminal GUI of server on my own computer. However, if I repeated these steps on the second server(Ubuntu18.04), I will got nothing to show on my computer.
The I execute commandgedit on the ssh login terminal when using ssh -X to login into both servers, I could see the GUI on my computer for both the cases.
I guess Ubuntu 18.04 cannot transport terminal's GUI through ssh -X to my pc. I was very confused about this. Could you please to explain the reason? And BTW, how can I see terminal's GUI of server in this case? Thanks a lot!
ssh -X doesn't transport a terminal. It tunnels a X11 connection.
X11 in its core is a network based display protocol. The programs (X clients) connect to a X server (a program running on your local machine) and instruct it to create windows and draw stuff to it. There is no graphical rendition of any kind anywhere else than the X server!
ssh -X does not operate like Windows Remote Desktop, where there is an actual graphics environment running on the remote machine. Hence if you create two separate ssh -X connections (maybe even from different machines), these connections are completely independent from each other. Hence you cannot use ssh -X to connect with a preexisting X session!
What you want is either Xvnc or Xpra, where the graphics environment is actually run on the remote machine, and only the output is transferred to your local machine.
I just can't connect to remote interpreter in Pycharm professional on my Mac. But I've connected to my interpreter very well in the past few weeks.
It is always showing "Connecting to XXX(my host ip)". I configured it with SSH Credentials and Deployment configuration. And I tested the sftp, it worked fine.
However, I can use my terminal to connect to my host successfully via ssh.
I just don't understand what happens.
I tried many ways and finally found that it was because I changed the default bash to zsh on my server. After changing zsh back to bash, it was fixed.
I need an sftp windows client and I just installed Bitvise. My windows 10 version runs on Parallels (version 10) on a Mac (OS X Yosemite version 10.10.5). As a test, I tried to open an ssh connection with the Bitvise client to the ssh server running on the Mac. I first went to the Mac, System Preferences -> Sharing and clicked on File Sharing and Remote Login (for all users, just to be sure). I can perfectly ping the Mac from Windows as well. Now when I try to open a connection from Windows to the Mac (Bitvise GUI or simply sftp from the command line), invariably I get this message.
The SSH2 session has terminated with error. Reason: Error class: LocalSshDisconn, code: ConnectionLost, message: FlowSshTransport: received EOF.
Does anybody knows what's going on? I couldn't find that error message anywhere. Just for your info I tried this from the command line
sftp mymacuser#my.mac.ip.address
And then again
ping my.mac.ip.address
works perfectly OK.
Thanks very much in advance.