I want to run a site which is on my different server with a host name.What can be the ngrok syntax.I tried running ngrok http -host-header=abc.com 80.But it shows tunnel not available.What can be the syntax for running a website which is located on remote server from my local machine.
It sounds like you are looking for the feature of forwarding to servers running on a different machine.
Take a look at the documentation here:
https://ngrok.com/docs/secure-tunnels/non-local (updated)
You should just be able to specify a network address and port instead of just a port with this command:
ngrok http 192.168.1.1:8080
Related
I'm currently trying to setup a tunneling tool, specific for game servers.
So you can start the server locally and everyone can join without open your ports or getting unsecure.
Basicly I do a reverse ssh tunnel to one of my dedicated linux servers where the game port get mapped to a different port (for example 8888). So the server is now exposed to the internet and available for anyone and the user don't have to get unsecure and open his own ports. Everyone can connect to the following ip: SERVERADRESS:8888.
The command which gets executed looks like this:
ssh -N -R "*:8888:localhost:25565" root#SERVERADRESS
This works fine just as i want. But I also want to secure my "forwarding" server, so I'm relativ new to networking but I found reverse proxy's. I watched some tutorials and I installed the "Nginx Proxy Manager" tool which comes with a web interface and looks very good and easy. So there is an option to create an Stream (Picture below), there you can enter the incoming port and the forward Host + port, for example: REVERSEPROXY:7777 -> FORWARDINGSERVER:8888. So with this I want to hide the ip adress from the server where all the ssh tunnels. Sadly this Stream tool won't work, I already saw some other topics with that. They all said to enter the port into the docker-compose.yml which I already did + restart. But for now it won't work. Any other soloutions for this problem? Or completly different ideas to protect my server?
https://i.stack.imgur.com/FolLe.png https://i.stack.imgur.com/KuJbt.png https://i.stack.imgur.com/2SN4a.png https://i.stack.imgur.com/9kzbj.jpg
I try to do my own tunneling tool, but with a protection so that my server getting damaged.
Not able to access nginx from outside the server
I have used ansible role written by me to download nginx on linux machines. But i'm not bale to access that nginx service outside of the server (the one on which it is installed)
https://github.com/kishanagarwal/ansible_poc/tree/master/roles/nginx
You can access the code from above url
I am able to get a welcome page of nginx service running on Centos machines, but can't get anything when i tried to access ip address of machine running on ubuntu 14.04 and having nginx installed on it.
Its simply means nginx port is not opened.
steps to follows:
login to your machine which is trying to access nginx.
if it is windows ,open DOS prompt OR if it is linux, open terminal.
run following command :
telnet
Based on output , if port is not open, you can refer following guide to open port:
https://www.cyberciti.biz/faq/howto-rhel-linux-open-port-using-iptables/
I'm trying to use Google's Colab feature to connect to a remote run-time that is configured with HTTPS. However, I only see an option to inform the port on the UI, not the protocol.
I've checked the Network panel and the website starts a WebSocket connection with http://localhost:8888/http_over_websocket?min_version=0.0.1a3, HTTP-style.
Full details of my setup:
I have a public Jupyter server at https://123.123.123.123:8888 with self-signed certificate and password authentication
I've followed jupyter_http_over_ws' setup on the remote
I started the remote process with jupyter notebook --no-browser --keyfile key.pem --certfile crt.pem --ip 0.0.0.0 --notebook-dir notebook --NotebookApp.allow_origin='https://colab.research.google.com'
I've created a local port forwarding with ssh -L 8888:localhost:8888 dev#123.123.123.123
I've turned on network.websocket.allowInsecureFromHTTPS on Firefox
I've went to https://localhost:8888 and logged in
Naturally, when the UI calls http://localhost:8888/http_over_websocket?min_version=0.0.1a3 it fails. If I manually access https://localhost:8888/http_over_websocket?min_version=0.0.1a3 (note the extra s) it gets through.
I see three options to solve it:
Tell the UI to use secure WS connection
Run a proxy on my local machine to transform the HTTPS into plain HTTP
Turn off HTTPS on my remote
The last two I think will work, but I wouldn't like that way.
How to do #1?
Thanks a lot!
Your option 1 isn't possible in colab today.
Why do you want to use HTTPS over an SSH tunnel that already encrypts forwarded traffic?
We are using NgRok to tunnel TCP/UDP connection from the internets to the localhost.
However, as you know, stratum has it's own protocol, and subsequently, the url looks something like that:
stratum://0.tcp.ngrok.io:3333
NiceHash, our hashes provider, does not recognise it, and thus is unable to connect.
Some background:
We are developing a mining pool and would like to test it locally, before deploying to staging / prod.
Please take a look at https://github.com/mmatczuk/go-http-tunnel you can host server on GCP and have any dns name you want.
I am new to using Grunt build tool. Suppose if I already have the required files in my "dest" folder how can I use Grunt to simply load the same to the server.
Also, I am currently able to access grunt service running on "localhost" on 9090 port.
But if I replace the "localhost" with my ip address, I am getting a 404.
I tried the same with my tomcat server but I am able to access the tomcat server on 8080 port via IP address as well. Please let me know what needs to be done to allow access via IP? I am using a Windows PC
In case someone stumbles upon this one, just change localhost to 0.0.0.0 in the gruntfile.
This is the reference: https://github.com/yeoman/generator-angular/commit/fbad1ab0ab789bb37fe5dfa40d5e8ada2f4fa0c5
It sounds like you are asking about how to copy files to a remote server using Grunt.
If so try either grunt-ssh if you have SFTP/SCP acceess to your remote server, or grunt-ftp-deploy if you only have FTP access.