How can I run ngrok service in windows background. I have tried ngrok http 80 --log=stdout > ngrok.log & but it just hide the status if I close the ngrok.exe terminal, the service also get terminate. Is there any ways to let the ngrok.exe terminal run on windows background? Thanks
Related
I have created a Nix repl for my project and it starts a web server in the background using nohup python3 -m http.server &. It works fine when I log in to my account and execute it, but when I log out, it doesn't run the web server in the background, but instead, shows the web preview. I tried using the embed=1&output=1 parameters, but it still doesn't hide the preview. Please help. Here is the link to my repl: https://replit.com/#Dark-cobra/WAFER
I have a script to test and make connection via Wifi. It works pretty fine for WEP and WPA2 AP when launched directly in the terminal.
But when the script is launched via a service I get a "deauthenticating by local choice" almost instantly when connecting to WPA2 AP.
Here is the script :
systemctl stop dnsmasq
systemctl stop hostapd
systemctl disable hostapd
ifdown wlan0
killall wpa-supplicant
ifup --force wlan0=wlan_orange
sleep 30
Thanks in advance for any help.
EDIT
I try to add a "sudo" to my ifup command but he has not shown any results.
EDIT 2
Long term test does not show any problems on WEP connection. I suspect that the problem may come from a network setup but I don't know where to start to look at.
EDIT 3
I found out that the deconnection appears after the end of the sleep. I confirmed it after several tries with different time.
I have a node.js server (with socket.io) running using upstart and monit. My problem is my server becomes inaccessible (usually happens when im offline), and the monit is unable to restart the process. The server only reactivates or awakened if i login into the ftp using filezilla.
This is my monit configuration:
set logfile /var/log/monit.log
check process mynode with pidfile /home/mylocation/pid/node-app.pid
start program = "/etc/init.d/node-app start" uid nobody and gid nobody
stop program = "/etc/init.d/node-app stop"
if failed port 8000 protocol HTTP
request /
with timeout 10 seconds
then restart
Any ideas?
I was able to solve my issue,. it was server software versions. If anyone still bumped into this problem, just upgrade to latest stable software versions. Mine works fine in ubuntu 12.04
When I try to run server(rc) in command prompt it is saying it is already used. So, I run the server in 5555 and changed the same in script. However, it still shows
WARN - Failed to start: SocketListener0#0.0.0.0:4444
Have you tried to stop the server using the below link?
http://localhost:4444/selenium-server/driver/?cmd=shutDownSeleniumServer
Just open the above link in the browser you are using to run the tests.
After the opening the above link, the selenium server stops.
Then you can proceed with starting the server from port 4444.
Close the browser that is running on port 4444 and then restart the selenium server
I had the same problem,
type this instead
webdriver-manager --seleniumPort 4455 start
it will start it on port 4455 (you can try different numbers as well)
I get a black screen with the above setup. I have tried RealVNC and TigerVNC clients too on windows with the same result.
Any ideas?
Thanks
It's possible your VNC server is running, but there is nothing running in it; no window manager, no desktop environment (GNOME), etc.
That probably means you ran the VNC server directly without using some of the friendly wrapper scripts such as vncserver. For example, if you run Xtightvnc directly, that's what you'll get.
For example, on Ubuntu I usually start a VNC session (or port 5901) like this which starts the VNC/X-server and the normal desktop environment:
vncserver -geometry 1024x768 :1
On Ubuntu vncserver is a link to tightvncserver. If you don't have vncserver on Fedora 13 then try tightvncserver.