I'd like to introduce you to ngrok which is kinda like Hamachi but more than 5 people can join the server
Arguably not really a commandline program, but I had a paid account for ngrok at my last job. I didn't have to use it very often, but when I did it was a massive time saver. The $5/month gave us a great return of investment; developing my own solution would be far more time-consuming (and thus expensive).
I'd pay money for:
an IRC client that doesn't suck. Yes, I know about the IRC client you're about to suggest; I think it sucks. They all do.
I'd pay money for a better email client. I currently use claws-mail (GUI) and it's kind of okay, but quite slow for many operations. I also have a locally patched version and upstream never responded (much less integrated) my patch :-( I used mutt, but it's too hard/complex to set up/learn, and I don't use email enough to justify it.
I use Vim for ... everything, and I think it's pretty neat but I think it can be done better. vis is perhaps a good start, although not working on my white background has been a bit of a show-stopper thus far.
Second this. It makes your local dev URL internet facing with a new URL generated every time you start ngrok. you can access the url on any device like normal.
This however means your Dev work is exposed to anyone who gets your URL, very very very unlikely but Always close ngrok after use don't leave to ports open for longer than necessary.
Easiest way to get SSL on localhost is to use ngrok. It tunnels to your localhost and exposes a unique domain with its own cert.
Also, just to quibble, SSL was deprecated years ago in favor of TLS. We only say SSL by convention.
You can use ngrok. It exposes whatever port you want to the internet and gives you a URL to access it. Your own pc will serve requests over this. Check it out here: https://ngrok.com/. It’s a pretty useful tool!
Thanks, this is really nice. I'm thinking about bioinformatics, where it could really shine. A lot of tools have to be developed and used by people who share their cognitive resources between biology and computer science. Correct me if I'm wrong, but thanks to minicli and ngrok for instance, usable web interfaces for local python tools could be provided almost for free to remote collaborators. I shared this idea on linkedin (very far both for the FLOSS culture and reddit, but that's where my network is :-/).
Ngrok has been the solution/saviour of many people who have ISPs that do dumb/unhelpful shit.
It's this simple to use. Use 30000 (the default foundry port) instead of 80.
Option 1: Buy a realm or hosted minecraft server from somewhere. Easiest but costs $$.
Option 2: Download MC server from here and then once you have it running download ngrok and run "ngrok tcp 25565" which will allow you to create a secure tunnel to your host on port 25565, allowing anybody to connect, skipping the portforwarding/other nonsense.
If you're interested in option 2 and have any questions let me know!
Because you need to forward port to make it work. This is a common problem in any multiplayer game where you'd like to host a server to play online with friends. This is where programs like Hamachi or Tunngle have use. Some Steam games use Steam Network to manage online connections. There's also a less-known tool called ngrok, which gives you a forwarded IP address through third-party server.
You may also want to give https://ngrok.com/ a try.
You simply download it, run it, and it exposes your localhost to the internet.
Super easy to use and you don't even need to be on the same network. In fact you can send the link to your coworkers, clients, or even your boss to review your localhost dev environment.
Pretty nifty!
Actually your ip address is the link, if you want to send the link to a person, you need to have open the port 80 using port forwarding, and that I will say now is something that nobody will say you but is very good, I use the most times Gmail to change the URL name, so if your URL is your ip you can make it appear to be another website. Other thing you can use if you don't want to do port forwarding is download Ngrok, I will give you the amazing opportunity of go straight to the internet an see what is ngrok, and how it works, here you have a link to the site, if you have any issues contact me.
-SS
I am using ngrok. There is also localtunnel, but I found the latter to be very slow, so I keep it only as a fallback option. Xip.io doesn't work for me either and I have been tinkering with my router and network settings for hours.
To clarify: Most "local" computers can not be reached from the Internet. They only have an internal IP address (e.g. 192.68.x.x) and the Internet router also serves as firewall blocking incoming request from the Internet.
There are 2 ways to solve this:
If you plan to host a website that runs 24x7 my advise is to use a cloud service or run it on a VPS.
Edit your settings.js
file, setting uiHost
to either '0.0.0.0' (IPv4) or ::
(IPv6, and depending on your OS settings possibly also IPv4). This allows other computers (but so far only on your local network) to access Node-RED. You may be able to skip this step if you choose to use a tunnel (see below).
Then you could use a VPN to access it as if you are still on the local network, even if you are not.
If you don't want to use a VPN, the next step is securing your Node-RED installation since anyone that can access it has a somewhat scary level of access to your system and network.
Then you could use some kind of tunnel (such as Argo Tunnel or ngrok).
If you have an externally visible IP, you can also instead open an external port and connect it to port 1880 on the machine running Node-RED (if you don't know how to do that, Google can probably help you there: search for the brand and/or type of router and "port forwarding").
Port forwarding will work. However if you just want to setup a quick test, I would usually setup something like ngrok which will tunnel the connection to your local machine. https://ngrok.com/
Imas par opcija:
Na nekom spoljasnjem VPS-u instaliras VPN i mozes da koristis ovo https://github.com/Nyr/openvpn-install samo zakomentarisi liniju 272 da ti ne bi sav saobracaj isao kroz VPN. VPS mozes da uzmes kod hetznera za 2.5$/mo; To je vise nego dovoljna masina za kucne VPN potrebe (PREPORUCUJEM!)
Druga stvar je da imas tipa teamviwer/anydesk pa onda na to da se kacis
Treca stvar https://ngrok.com/
Cetvrta stvar hammachi (koji mu dodje isto kao vpn)
To actually answer the question, rather than parrot server hosts like everyone here loves to do:
You can get a static domain with ngrok, just not with the free plan. https://ngrok.com/pricing tells me that you need at least the pro plan for reserved TCP addresses, which is what you want. Here are the official docs on how to set it up: https://ngrok.com/docs#remote-addr.
I think this basically comes down to: you and your app developer need to sit together and debug the thing.
Ask him to change the server address to point to a version of your Rails application running on your local machine (connecting to that should work just fine from within the same wireless network once you tell your rails server to listen on all interface by starting the server with -b 0.0.0.0
). Alternatively, if you're e.g. not working from the same location, or your network blocks the access, you can use https://ngrok.com to give him a publicly accessible version of your local Rails server.
Next set breakpoints in the controller actions, models, etc. and step through the calls, checking results, making sure that data is as expected and records are actually saved.
In order to make the server reachable when someone connects to your public IP, you need to be able to forward the port from the host computer. If you do not have control over the IP address, there is no way to make it point back to you. What is however possible is making an external service forward the data: https://ngrok.com/.
usually i'm using https://ngrok.com/ to forward local ports for presentation.
for permanent solution i'm using nginx proxy container:
Tip: Once you figure this out and want to catch Pokemon on the go, download and install ngrok. Follow the relatively easy installation instructions and open the URL it spits out on your phone. If you leave your laptop running with something like Caffeine, the script will keep executing while you go hunt Pokemon.
A few lines below that, you will see two strange-looking URLs, http and https--these are randomly generated secure URLs that can be used by any browser, regardless of whether it's inside or outside your local network. It will look like this: https://#######.ngrok.io
Enter that https URL into any browser (including the one on your phone) and you'll be accessing that local port through a secure connection!
Hope that helps. :) I used this yesterday at a park and bagged my first Tauros.
Pro tip, you can use ngrok or localtunnel to test your local code on actual devices, easily. Or you can configure a virtual machine to run your local site on a specific IP address which can then be accessed directly by any devices on your network.
Either way, you'll want to be testing directly on the target devices. And, since there are 23483829423948324 device/browser combinations, you'll want to make sure you enumerate a guaranteed finite set of them in your contract, and base your pricing off of how many guaranteed devices you support.
Another substitute for no-ip is https://ngrok.com/ which forwards your localhost to a remote *.ngrok.com address so that anyone can access it. It allows you to inspect packets and replay data as well which makes it much more valuable than a simple forwarding program IMO
Also if you are looking to just serve a few files and support websockets, I wouldn't download apache for that. It'd be much simpler to use node.js and npm install https://www.npmjs.com/package/websocket In that package, there are a good number of example servers and clients available. If you'd rather use socket io, there is a node package for it as well https://www.npmjs.com/package/socket.io
If all you need is a simple file server, you can run the following command in your directory that you want to serve and it'll be available at localhost:8010 (or whatever port you choose)
python -m SimpleHTTPServer 8010
Looks like you can do it with the $8.25 a month plan, not sure about the $5 plan, you can find the pricing here. The documentation for whitelabel domains etc is here. I think you may be able to do it with the $5 plan as seen here since you can make a custom subdomain with the $5 plan but I'm not 100% sure since I've never used ngrok's paid plans.
What u/BrianBoyko said.... but you can use ngrok free tier
I am not sure if you can go out to their proxy but it won't cost you anything.
It is probably blocking internal traffic on the ports you are using. Either way it's probably missing certificates or network tokens to communicate peer to peer internally
Hi guys, I have published a blog post showing how to use Nginx Proxy Manager and Husarnet P2P VPN client to expose services hosted by local machines (laptops, Raspberry Pi etc.) to the public Internet.
So end result is something similar to https://ngrok.com/. Next to just NPM configuration (that is super easy!) I show for newbies how to setup DNS and obtain a wildcard SSL certificate allowing you to define a subdomains just from a level of NPM.
I hope you will find that useful.
Możesz próbować otworzyć tunel na świat przy pomocy ngrok, lub localhost.run. Obie usługi płatne (ale mają darmowe plany), aktualnie korzystam z tej drugiej.
It's pretty easy but you'll need a windows or Linux machine on 24/7 to forward the connection. Basically just a command line directing to a specific ip and port. I believe you have to use a token generated on their website in your account to set it up initially but it's all pretty easy. The free version only allows 1 connection and the url will change if the instance stops and has to be restarted. The $5/month one offers domain linking and more connections but the free one works fine for me.
If you want to test it out locally without setting up a webserver, DNS, etc., you can use https://ngrok.com/. It will give you a publically accessible URL and then you can configure the webhook service to hit that URL.
For more long-term solution, you will need a VPS or something like AWS Lambda with a publically accessible domain.
so, as I understand, you mean on same LAN. you can couple it with project like ```ngrok``` and can generate a url for the flask server (example, ```ngrok http 17171```) and that url you can share with others. I generally do it while working with other engineers in my team. But on it's own, you can use it for your local network.
Ref: https://ngrok.com/
The problem with a homeserver is how to route traffic to it? Assuming you don't have a managed local network, I suggest you'll need some kind of tunnelling proxy. Some options to consider:
These products enable your ingress controller to accept connections via a public DNS name. A big advantage of this is that you can use solutions like cert-manager to secure your applications using SSL.
In short you can operate a k8s cluster on-prem in the same way it would work on the cloud
If I understand correctly you are saying the bug is that the trashcan is not choosing 20 Mhz channel width for your ras pis when trashcan is set to use auto for the channel width? If so, that's a misunderstanding of what auto means in this context. Auto selection of channel width by an access point means it does RF scan to see if enough adjacent 20 mhz channels are free such that I can take 40 mhz and if not it will use 20 MHz in order not to interfere with the neighboring 20 mhz width channels. An access point only can operate at 1 bandwidth at any given time and cannot selectively change per the device connecting.
The trashcan supporting port forwarding is not the only issue for that to work. IPV4 on tmobile is CGNAT and your modem is never getting a publicly routable IP that you could connect to. IPv6 appears to be filtered upstream by tmobile and no inbound requests even hit your public IPv6 addresses.
For your use case on the pi's though I bet you could use something like https://ngrok.com/ to get a tunnel that will allow you to port fw back to ALLSTAR and ECHO-LINK.
Most VPN providers dont allow you to port forward through the vpn.
However you could use something like localtunnel or ngrok which function as a single port VPN tunnel, they are usually used for times when you can't portforward, but would mask your IP.
What about https://ngrok.com/ as something similar that doesn't require a server somewhere else? You still establish the tunnel from your network/host and they provide you with an external URL. The paid plans are needed to have URLs that don't change all the time.
I haven't tried using ngrok for this, but your post made me think that it might work.
what's infrastructure?
IIRC you can use ngrok (limited free) or Cloudflare's Argo Tunnel (paid) to tunnel your in-home webserver to their public-exposed servers, or if you already have a public-facing server (i.e. a VM or a cloud instance), you can use SSH tunneling from your in-house server to the public-facing server, and serve from said server.
My assumption with Sim internet is that your router doesn't have a public IP that matches the whatismyip.com address.
You may have a CGNAT through your ISP. I assume the router WAN IP is in the 100.64.0.0/10 range (100.64.x.x – 100.127.x.x)?
You could use something like https://ngrok.com to give you a public way of accessing the service. There are also alternatives you can look into at https://alternativeto.net/software/ngrok/
Are you sure you can't self-host? If you have the bandwidth but just not the access to the router, something like ngrok would allow you to create a VPN for you and your players to tunnel through your router.
My brother and I were able to get a Minecraft server running through ngrok. https://ngrok.com/
I don't know much about it nor have I set it up myself, but it's the only thing we've gotten to work through different efforts. We haven't tried any other games at the moment though.
Here's what I did and it works like a charm (however your computer will need to stay on since the server is hosted on your computer).
ngrok installs as its own binary and has no dependencies, so it doesn't need Node or anything else to work.
However, it's not a server itself, all it does is "tunnel". That basically means that ngrok's server can talk to your computer, and it exposes that via a public URL. Something has to be listening and respond; if you're using any kind of development server this will work. It just won't help you if you aren't serving these files somehow.
Dev tools has a device simulator which is probably the easiest way. Open the dev tools menu in the browser and hit the 'toggle device toolbar' icon top left. You can select multiple window sizes (including actual branded mobile devices).
Alternatively, use https://ngrok.com/ to create a 'tunnel' to your localhost which you can access on your actual mobile. Then you can test how it feels in-hand, swiping etc.
Reminds me of ngrok, which gives you a link and all the requests made to that link will be redirected to your localhost without any port forwarding or web hosting. Very useful for showing people your projects and testing your backend projects with webhooks.
Easier solution to bypass port forward:
Download ngrok from here https://ngrok.com/
Run it from the command line ./ngrok http 3415
Give the url that is displayed to the exchange. Should be something like https://xxxxx.ngrok.io
Your listener should be already running on 0.0.0.0 i.e grin-wallet listen -e
before all that
Keep in mind that you are trusting ngrok to not man-in-the-middle you but at least it's over https and your ISP could do that anyway (it can't now)
Alternatevly if you are on windows download Grin++ v0.5.3 or later that come with ngrok support and takes care of all that for you. head over to the receive panel and you will find your ngrok address (keep in mind it changes every time you restart it)
There is also Ngrok that forwards a tcp connection to their servers. So only tou need it and you forward the Minecraft port to it and it’s spits out a ngrok connwction. Instead of a vpn to make the game think your in the same Network. This tool actually port forwards the port to their services and lets you connect.
Why not setup ngrok? It provides a tunnel service regardless of your IP. You'd run it on the system you want to serve data from (the host) and point other requests to the URL that ngrok provides.
You could try using ngrok free tier if it's just for personal use, gives you an url that tunnels to localhost. I've used it when demoing sites for clients without having to host it elsewhere, works pretty well.
No problem - we all started somewhere.
For demoing: We'd normally call this a "staging" environment, which should be a clone of your production environment, except running the latest code. You'd demo new code there. Once approved, you'd release it to your production environment. This isn't necessary if your production environment isn't in use by actual users yet. Once it is, though, you'll want to follow that pattern so that your client has the opportunity to test your changes and provide feedback before releasing them to your users.
If you don't want to set up a separate staging server and want to demo some of your development progress, check out ngrok. I wouldn't personally make that part of my normal review workflow, but in a pinch it'll work.
Git: You should view your git repos as totally separate from your servers. Git is where you manage the history of your code. At some point, you'll want to release your latest code to a server somewhere. You'd typically do this by copying your latest code to your server(s). This is often done in an automated fashion (e.g. Capistrano), but could be done manually as well. A manual process could look like cloning your git repo to the server (just for convenience), then pulling the latest code when you are ready to release, and rsync'ing or cp'ing the latest code to whatever your web root is (e.g. /var/www/ or whatever). Deploy systems will add some other fancy stuff on top of that, but that's basically all they are doing.
It sounds like you want to push your code and have it deploy. You should generally avoid this. Make deploying an explicit step. A common workflow for myself is to: push my changes over and over again onto a feature branch until my work on that feature is complete > deploy the feature branch to staging > have client review feature > merge feature branch into master after approved > deploy master branch to production.
Something like ngrok: https://ngrok.com is a really powerful and generalised solution
More specific ways exist but need set up per device, and the process can be different from device to device, eg, this for android: https://developers.google.com/web/tools/chrome-devtools/remote-debugging/local-server
If you just want to test a website from localhost, I suggest ngrok.
You run a command in your folder, and it's reachable from a random URL.
I use it sometimes to test services that want a callback URL, for example for authentication. Or when I need a quick way to test something I did on the iPad / iPhone
You have couple of options here. You can configure your router to forward packets from outside port to local IP/port. You can also use https://ngrok.com/ to the forwarding for you (read how to use it).
A great way to put a local site online is ngrok but it's just for testing / development purposes.
When you are ready to publish it for the outside world, you need to put it on a web hosting.
Do you have a static IP address? could you open up the firewall to allow https calls through to your web server? I think that would be the easiest. If you don't have a static ip address, you might want to try a dynamic dns option.
I've used https://ngrok.com/ while developing a flask app that makes/receives calls from twilio. This works great, but the url for the free version will change every time that you restart the ngrok service.
Good luck!
Not sure if IFTTT supports it but you can make it a bit safer by specifying a non-standard port rather than the default of 80. Typically this is done by appending the port number to the URL like http://www.example.com:8008 (uses port 8008 instead of 80). You then set up port forwarding in your router to translate 8008 on the WAN side to port 80 on the LAN side. This is, of course, a bit like hiding your spare door key under the 3rd garden gnome rather than under the doormat- a determined attacker will still find it. Some routers allow you to restrict access to forwarded ports by IP address which makes it somewhat safer again . Even TCP/IP is still going to need some kind of port forward.
The only alternative, unfortunately, is to stick another device (eg raspberry pi) in front of your ETH board and use that to somehow call out and use the results to manipulate the ETH interface. You can use a service like https://ngrok.com/ to give your RPi a public internet address but it will still require a bit of coding in the background to turn an IFTTT web request into something that the ETH board can understand.
If you really just want to keep it local for now, use something like https://ngrok.com/ that will create a tunnel to your localhost, but you need to make sure your computer stays online.
Other than that, look for a hosting service that offers free trials and quickly upload your website: https://www.wphostingreport.com/free-trials
Or take a look at digital ocean and create a cheap droplet for preview purposes.
You could use <code>ngrok</code>. One command will get you a public URL over HTTPS that tunnels directly to localhost without those types of issues:
ngrok http -host-header=localhost $YOUR_PORT
You should be able to connect to the web server locally on your LAN. Probably won't be able to connect to it from the outside if you can't open the port unless you used some NAT punching thing.
How about VNC with ngrok? It shouldn't be too hard to make a script to automate the whole process. It would have to do something like this:
Package a portable VNC client, the ngrok client and this script up, upload it to dropbox, google drive or a self hosted server and send the link to the remote users.
The only downside is the hard-coded ngrok account in the script, but this isn't a problem if it's only for supporting family members.
Yep, if you use Vagrant's Caddy server for your development environment, it includes Ngrok (https://ngrok.com/) which is mentioned above and is implemented through the vagrant share command.
The only downside is that you need to keep a terminal window open the entire time or keep the share process running in some other way for your site to stay viewable.
If you need something more stable, you might just want to get yourself a low-cost DigitalOcean server and setup webhooks for automatic Git deployments.
You can setup the map on your home computer/laptop and then view it view in any web browser so you wont need any admin privs. The downside here is any config changes will need to be done on the home machine.
Something like this:
https://ngrok.com has worked well for me in the past, but I think they have changed how they charge and what's allowed in the free version. Haven't needed it in a while.
If I needed to get to my pi and it was home, I'd ssh to my home server, an Ubuntu box with SSH running and open and then ssh to my Pi from there.
(I was wondering the same thing, so I decided to try setting it up. Just did and it works.)
:-)
Do you have TightVNC installed? Get that set up and running on the PI, within your local LAN first.
Ngrok is a free, very handy utility that most people use for temporarily making a web page they are working on locally, available to someone outside their LAN. You can also forward other ports and protocols, though, so it works for what we're doing here.
Download ngrok. Unzip it and you'll have a program called ngrok sitting there. Run it in the terminal by adding "./" in front, like "./ngrok"
Create an account. I used Github auth. (You can also use Google or email.)
Go to this page and look for the line like:
./ngrok authtoken XXXXXXXXXXXXXXXXXXXXXXXX
Run that. That lets you forward ports to their network.
(At this point it would be handy to install Screen or TMUX so you can leave the following commands running after you log out.)
Next, figure out your TightVNC port, probably 5900 or 5901. (5901, in my case.) Run:
./ngrok tcp 5901
The resulting page will have a line that looks like:
Forwarding tcp://0.tcp.ngrok.io:12345 -> localhost:5901
Since I use OSX's built-in VNC, I go to finder and hit Cmd+K to open the "Connect to Server" pane and change the line, taking off "tcp:" and changing it to "vnc:" and dropping the junk at the end
vnc://0.tcp.ngrok.io:12345
As I said, I just installed this on my Pi and it worked. Your mileage may vary.
ngrok is what I'm using. Download it, unzip, open up cmd window where the ngrok.exe is, type in 'ngrok http 5000' (assuming your map is on localhost:5000). Another cmd will pop up and on the line with "Forwarding" there'll be a randomly generated url, type that into your phone's browser and you'll be able to see the map.
If you would like your localhost to be accessible by anyone over the internet the easiest way I can suggest is using Ngrok. Read through their documentation, it will allow for others to access your html public folder as a "website".
Since your public (wan) ip is likely to change (unless you have configured a static ip with your isp), you can use a service such as http://www.noip.com/ (there are probably others, but I've used noip successfully) to automatically update your dns records when your public ip changes.
But yeah, if you have a static address, then any domain registrar that also supports dns will do (although I suggest you avoid godaddy in favor of gandi.net, easydns.com, or namecheap.com). Just set your domain name's A record to point to your public address.
edit:
Another method, albeit a little messier, would be to use ngrok to make your site publicly available without port forwarding or worrying about your public ip changing, and then use stealth url forwarding to point myname.com to whatever domain ngrok gives you.
ngrok is awesome for tunneling to a local machine behind a NAT. You run ngrok on a home machine, and it gives you a URL. You can then access the tunnel to your home machine via the URL from anywhere (for example, from your VPS).
There's a free-forever option; check out ngrok's pricing for more features/connections. If those plans don't work well for you, I encourage you to email nrgrok's creator to work something out for your setup. He's been very flexible with me as a student :)
ngrok is without a doubt one of the best tools I've ever come across for things like this - debugging webhooks, oauth callbacks and the like. They terminate https on their end and proxy it through to your dev server. Worth the $60/yr for a reserved subdomain, so you can set up all your redirect urls, webook urls, etc once and be done.
You could use something like https://ngrok.com/ to make your localhost accessible to others from outside your network. Furthermore you need to use a Wordpress plugin to force your WP to use relative paths, there is help to it in the ngrok FAQs, take a look at it. The only thing here is that your desktop at home needs to be running for this to work.
Some solutions that work with ACT.
Also see,
IDK nothing about the miner world, so IDK about why you need to bypass CGNAT.
Using a SDN is just to connect 2 nodes through the internet, but since it is software controlled, you need to have control over the 2 nodes. So this is useul to connect your sister house to your house, and you can share files, or play a game over "LAN"
depending of what you want to do you can test using ngrok.com . It is a entrypoint to so others can send a packet to a address in ngrok and ngrok will forward to you.
If what you want to do is access your stuff you don't need a VPN. You can use ngrok. As long as you don't mind that they assign the name of your access, it is free. Or you can spend $5/month and use your own names.
You can use ngrok command to quickly start an HTTP server without opening ports on your router.
But yeah, I'm also disappointed that Live Share doesn't seem to work with Live Server; and that I can't simply display the preview tab open in my editor, even though I have a shared Live Share session. It is counterintuitive.
i also didn't understand why my ip wasn't reachable until i learnt in school how it works, so i will try to explain it as easily as i can, i know its still long but its pretty complicated.
it all starts from when computer people were decinding on how to make the ip to connect 2 computer toghether, the tought that having an ip that ranges from 0.0.0.0 to 255.255.255.255 (4.2 billion total) was a good idea.
unfortunately they didnt know computers were about to get incredibly popular and affordable, and the number of computers connected to the internet is now more than that (or at least close to that number).
so to prevent the possibility of a disaster with 0 avaible ips, networking companies started using NATs server to, in very very short, link just 1 public ip (for the NAT server) to many (up to 63 thousand) "under" him, at the cost of those not being reachable (unless they send you something first).
that's (probably) why you are not reachable from the outside.
you can ask your internet privider to give you a public ip, depending on your contract it might cost something like 1 or 2 more dollars every month or be completely free. i was lucky enough that my provader gave it for free :)
i also use this when i'm not at home, its has a similar outcome of hamachi, but only you have to do things.
its called ngrok.com, you have to make an account, choose the free option.
it basically gives you an ip on their domain (ngrok.com) but it redirects its traffic to your pc.
if or when you get a public ip, it will be your router that has the ip, so you will have to do some port forwarding on your router's website. just google "[insert here your router model] port forwarding how" and you will find it.
I set up a auto-start service on the RasPi that establishes a reverse SSH tunnel to one of my EC2 servers on boot.
ssh -i ./my_ec2_private_key -N -R 3333:localhost:22
<code>my-ec2-server.com</code>
Then from a console on the EC2 server, I can SSH to localhost:3333 which opens a console to the RasPi.
ssh -i ./my_pi_private_key pi@localhost -p 3333
Doing this does not require a local port forward, or even knowing what the IP address of the RasPi is.
ngrok kind of works the same way, except you don't need your own intermediate server. You connect to ngrok from the RasPi using the ngrok client application and establish a tcp port that you can SSH or RDP to directly. If you are using the free version where the port changes every time you connect, you can use the ngrok dashboard to show you the port to connect to.
Note that regardless of either option, it is best to disable password authentication and only allow public key/private key authentication instead.
You can easily set up something like ngrok or Serveo and forward a port from your home PC to Internet. Great for prototypes. Some other alternatives are available.
Si te lo cambiaron de la empresa, vas a tener que morfarte el llamar para que te lo pasen (a menos que usen la misma contraseña en todos lados, que viniendo de acá es posible). Yo ese router lo compré aparte y no es muy jodido de configurar, viene con instrucciones bastante sencillas, pero no vaya a ser que se te descalabre todo...
Si lo que querés es abrir un puerto TCP temporalmente, ngrok te puede servir para sacarte del apuro, es fácil de usar y a menos que necesites algo más de 24 hs (o un dominio fijo) te ayuda una banda.
Espero te sea de ayuda, abrazo!
Ngrok is a program you can download on windows/linux and possibly mac. But what it does is it tunnels your connection on the server so others can join outside of the network it helped me when i could not get port forwarding working i am not sure how it works on bedrock but i have a link here https://ngrok.com/ alternatively see a yt video on the topic search “Minecraft server with ngrok” or something
Si hay una forma pero es totalmente ajena a Totalplay. Es imposible hacerlo con ellos a menos que les contrates un enlace dedicado, lo que te costaría más de 3 mil pesos mensuales por una conexión de como 30 megas simétricos. El otro método es con una madre que se llama "ngrok". Puedes usar el servicio gratuito pero tiene el inconveniente de que cada vez que se caiga tu conexión, te asignan una URL nueva que actúa como tu IP pública. También te limitan a 1MB/s de transferencia por conexión. No es tan user friendly el asunto pero una vez que entiendes cómo funciona, es una maravilla. Te permite exponer cualquier servicio sin tener que meterte con ninguna configuración de tu equipo de red porque funciona con una conexión inversa. Es decir, el servicio conecta la aplicación cliente que corre en tu servidor hacia ellos y ellos reciben el tráfico por tí, redireccionándolo a través de la conexión que ya estableció el cliente en tu extremo. Checa la página, el servicio es gratis pero si necesitas algo fijo y que no esté tan restringido, tienen paquetes según lo que necesites. https://ngrok.com/
I can't help you with the Elm side of things... but I can say that the Deno code you have above works as expected for me.
That is, if I cut and paste your top code block into a file (listenAndServeTest.ts) and run:
deno run --allow-net listenAndServerTest.ts
...I can load http://localhost:8000/ in the browser and get "Hello World" as a response.
I assume your Elm code is what's sending the request to your server? (I think you might have changed the contents of https://ellie-app.com/fvw36BRmWW2a1 since originally posting...)
If so, where is the Elm code running? If your server is running on localhost your calling code will also need to be on localhost in order to reach your server.
If your Elm code is on a remote server, you'll need to somehow make your computer/localhost visible to the outside world (potentially dangerous, so not a long term solution but ok for testing). Using a service like ngrok is probably the easiest way to do this.
I have T-Mobile 5G home internet right now. I used a UDM-Pro. If you want to avoid double NAT, your best option is to port forward things you want on your main router so its only a single NAT, but if you need to access something away from home, you'll either need a VPN with port forwarding such as Windscribe or you could try ngrok. (I don't use it, I've just heard good things about it). Also, the gateway will not forward your router an IPv6 address. So, that won't work.
For development environments you shouldn’t have to do anything. It depends greatly on what you’re programming with but generally your own localhost is used by every development system.
I strongly discourage you to use your home system for production environment.
Here’s something on setting up home servers though
The most important point is only expose what you need to the internet.
Setting up a home vpn should be used for any access or anything that doesn’t 100% need to be exposed to the public
If you need this for some temporary work or some other use case Ngrok can provide external links for tunnelling your local development environments over https
Generating your own self-signed cert is an option.
My preferred method is to use Charles proxy (others will probably work as well). I run a mock server which runs on port 8888 HTTP, and have a "Map Remote" configured to proxy my main HTTPS URL to it.
Another option is to using something like NGrok which will you give an URL that uses their certificate: https://ngrok.com/
I think we need a little more info about what you are trying to achieve. Are you trying to share your coding project with friends? What do you mean by 'access' the tab - are you going to allow people to write to that tab?
Just a guess, but if you are trying to share a project with friends, https://ngrok.com/ is a way to use your PC as a server and it is somewhat safe - but if you open your computer up to the internet just remember that the NSA got hacked. It doesn't matter what security you have it is definitely a risk.
Check out ngrok. Someone posted it on the Facebook T-Mobile home internet page and I set it up. Works good and it's free so long as you don't have a bunch of traffic outside of personal use.
I set it up for my blue iris server and worked like a charm.
Looks like Tor Browser redirects localhost/127.0.0.1 to HTTPS due to HTTPS Everywhere, and you most likely don't have HTTP/TLS set up there, which results in an "Unable to connect" error.
One thing you could perhaps do is to expose the server publicly using ngrok. This is free and will give you a temporary domain name with HTTPS, and works with Tor. Others shouldn't be able to guess the domain name, but you should still consider security in this case.
Unfortunately, as many pointed out, you won't be able to do much in the way of port forwarding. You can use a reverse tunnel to accomplish this, but it does require at least one publicly accessible machine live outside your home network.
This is easy to do and will work on any cloud provider, but will cost you actual money to run a compute instance, unless you're using free tier. You can always see if you have a friend or family member willing to let your tunnel process run for you, but availability is completely out of your control. I haven't tried this personally, but ngrok is basically a Reverse Tunnels as a Service: https://ngrok.com/. They offer a pricing option if you want to point your domain's DNS CNAME. Right now, that's about $12 a month. Your basically paying for their AWS bill at that point though and you might as well DIY it yourself for the same cost and all the control by running your own EC2 instance: http://imgur.com/a/8dIo45m
If you're looking at cloud at that point: you can go even cheaper and use static hosting depending on your needs, but I'm going to assume you don't want to go that route since your in this subreddit lol
hamachi is known to cause more issues that it's worth. For this, i would recommend using Ngrok instead.
If you are not using LAN, you will need to start up a server (Paper, Tuinity, Forge, Fabric, etc), and port foward the port 25565 (and if using Geyser, port foward 19132 as well)
You need the public IP of the other router and that router needs to be port forwarding the connection port. If you can’t port forward through the router, you’ll need a website that will let you reverse ssh through them like ngrok.
Hey I don’t want to disappoint you or anything but something like this already exists.
This doesn’t stop you from making your own service though and letting customers/friends use.
It’s a nice way to get around having a dynamic IP address if you want to host a public server.
that link goes to your local PC, use a service like NGROK or port forward tht port from your PC to the outside world and then send us the link to it
Hamachi is known to cause more problems than worth. Ngrok is usually better at this. Or run Nginx and bind it to the port that you want for a reverse proxy within the nginx.conf file
You always have the option of self hosting it (from your own network). If port fowarding seems like a risky move, try using Ngrok (which basically is another way to bypass port fowarding). Using a vpn is usually very unstable (especially hamachi) most of the time
For self hosting, as long you only port foward 25565 (for java), and/or 19132 (for bedrock support using Geyser), and made sure that the firewall is tightened well, you should be fine. For DDoS Protection, you can use Cloudflare or TCP Shield, you should be fine. Both are free
You could use a service like ngrok. It‘s basically a software you run on the computer that hosts your services. It creates an outbound tunnel to ngrok, which then exposes your service through their infrastructure.
An enterprise technology that does something similar would be Microsofts Azure Application Proxy.
You could also host it from your same system, but use ngrok to tunnel it out to your 5 friends. Then give them the tunnel hostname (if you use the free account it changes every time you run it). When you're done for the night, close ngrok, and the tunnel to inside your network is closed.
ngrok also supports passwords if you wanted to do that. Example could be:
ngrok http -auth="username:password" 30000
(You'd ideally want to use a better username and password though)
ngrok does support IP whitelisting, but it's through their website account management interface and might be unnecessary for your needs with the other compensating controls. (it's also a paid feature, so there's that...)
I have no experience of Starling.
However, I note that /u/icecreamhead said that it won’t work if running on localhost.
This makes development a real pain. I had the same problem with Sagepay. I found https://ngrok.com, which lets you easily set up a non-localhost address that points to your localhost development environment. There’s a free tier that does what’s needed to get around this kind of restriction. I have no idea if that’s a sticking point for you, but if it is then I hope this provides a solution.
If you've correctly forwarded TCP traffic on 4000 from your external IP to your local machine, you should be able to get it working. However, there are any number of weird issues you run into trying to expose a LAN device to the outside world if you're not using an internet provider and plan specifically tailored to hosting. The most common issue is that your ISP may be blocking traffic on certain ports on your modem, so even if your router is configured correctly the traffic may not even be making it there.
If you want, you can try a hosted service like ngrok that tries to circumvent common issues by proxying all traffic through their own servers, but your mileage may vary. Generally, using a dedicated remote host is the path of least friction.
It's a service that does SSH tunneling. SSH tunneling is essentially a VPN that runs on only one port, tunneling traffic from an open port on a server somewhere directly to your computer. It doesn't require port forwarding to work, but you'll most likely have to pay for it since there are servers on the other end.
EDIT: If you're interested: https://ngrok.com/
The thing is, others need to have iPv6 too, its less common that you'd thing. If you wanna see if they have iPv6, tell them to go to ipv6.google.com and if it works then they should be able to join
the only solution ive found around this is to use this program called ngrok. you would use it using the command 'ngrok tcp 25565' it works with people with ipv4 too and didnt take me long to set up, you also dont have to port forward with this.
i just realised you said you have a static IP, thats the one that costs £5 a month right? why would you wanna use ipv6