-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: connect EPERM //./pipe/rpc.sock #12
Comments
Hi @rossm-mf, That looks like an error that occurs when you attempt to invoke Make sure to right click and say "Run as Administrator" when starting a new console session. Hope this is helpful! |
I was using windows-terminal and for some reason it was not working. Now after few reboots, it's fine. |
Hey @rossm-mf, I'm a pretty big fan of Windows Terminal, but it does come with a few caveats that I've noticed while working on this project. One is that (unlike the standard Powershell interface) you can't right click the icon in the task bar and select "run as admin." Instead, you have to search for it in the Start menu and select "run it as admin" from there. I believe this restriction has something to do with packaging the app for the Windows store, but I'm not entirely certain about that. Another issue I found is that opening up a new tab inherits the environmental variables from the initial Terminal process, so it won't contain the latest ENV values. For example, after the Regardless of these minor roadblocks, I'm very excited about Windows Terminal and can't wait for it to ship standard in Windows. Glad to hear everything is working for you now! Hope this was helpful anyway. |
Description
Installation went well but I have an error when I try to see if pm2 is running with
pm2 ps
. I googled a little and some people talk about run as admin, which I already did. It seems to be related to the way we install pm2 on the machine. maybe you guys can help me on that part.Steps to Reproduce
pm2 ps
The Error
Environment
I ended with that on my global package list.
The text was updated successfully, but these errors were encountered: