localtunnel | expose yourself behind NAT or firewall to the world | Firewall library

You can use https://github.com/Miserlou/Zappa to deploy your flask-ask application.

Tutorial available here : AWS Alexa deploy on aws lambda using zappa

If you are absolutely certain that you solved all vulnerabilities you'd like to skip the audit, you can do so by appending --no-audit.

npm install --no-audit

or npm will fix for you

npm audit fix

But this will update version of modules. Which might lead to breaking of code.

You could always use the screen ruler (see S/O post here) and resize the window to the aspect ratio your checking. Hope it helps!

Edit: Another option

If you have the space for it, you could run android x86 (~3-4gb) in an emulator and adjust the emulators screen resolution (this one of the many things I need android x86 for)

Edit: Localtunnel appears to be working again. (Of course depending when you're reading this it may not be. Please use your own judgment.)

Original answer:

The cloud-hosted part of Localtunnel is currently down. You'll have to wait until its maintainer brings it up again, or use another service like ngrok.

Some more issues tracking this:

• https://github.com/localtunnel/server/issues/40#issuecomment-344038789
• https://github.com/localtunnel/localtunnel/issues/198
• https://github.com/localtunnel/localtunnel/issues/199

It could be a problem with localtunnel or your localtunnel connection, maybe involving SSH. You could run DEBUG=* npx localtunnel -p 8000 and see if you get an error message.

FWIW, I am currently getting the message localtunnel:client tunnel server offline: unable to verify the first certificate, and it is not returning the subdomain.

If you expose your database to the world with a weak password for a database superuser, that will definitely lower your security in a substantial way. Hackers routinely patrol for such weak settings and exploit them, mostly for cryptocurrency mining but also to add you to botnets. In those cases they don't care about your database itself, it is just a way in to get at your CPU/network connection. They might also probe for valuable information appearing in your database, in which case they don't even need to be a superuser.

If you always run the latest bugfix version and use a strong password (like the output of pwgen 20 -sy -1) and use SSL or if you correctly use some other method of authentication and encryption, then it will lower security by only a minimal amount.

If you personally control every password, and ensure they are strong, and test that they are configured correctly to be required for log on (e.g. intentionally enter it wrong once to make sure you get rejected), I wouldn't worry too much the port forwarding providing bad guys access to the machine. If you care about people being able to eavesdrop on the data being sent back and forth, then you also need SSL.

Encrypted tunnels of course are another solution which I am not addressing.

I didn't find out how to always get the first line of a stdout but I ended up not over complicating the problem by checking if the variable is empty before checking the stdout

Thank you for adding the error logs.

If you're adding POST data as a string but that's in a valid JSON format, it will be parsed as such. In order to preserve it as a string, you need to add a newline char or whitespace so the beginning of the string:

"\n

You're hitting a parsing error in the ethereum-bridge due to it trying but failing to parse the returned json from your query.

However at the time of writing, your local tunnel is returning a 404 error rather than the data it originally returned.

Then, as the ethereum-bridgeattempts to parse thejsonto pluck the value from thea` key, per your query:

json(https://purple-squid-54.localtunnel.me).a

...it can't because there is not json and so no a field and so you get a parsing error.

To fix it, ensure your local tunnel is working and that the data returned is in correct json format, and that there is an a key present for the parser to work with.

It depends.

They certainly don't copy your django code and run it on their own server and they're not going to maliciously grab files off of your machine.

They just read from a network socket, but they do vary as to how encrypted they are or aren't.

Telebit always uses end-to-end encryption via SSL, TLS, HTTPS, or Secure Web Socket (WSS)

• TLS certs happen on the clients, not the relay
• Works with SSH, OpenVPN, etc - but requires a ProxyCommand / secure client
  • (i.e. sclient, stunnel, or openssh s_client)
• Can work with other, normally-unencrypted, TCP protocols (requires a secure client)

There is a poorly documented and deprecated feature for raw TCP, which can be seen, if used.

serveo uses ssh port forwarding, which encrypts between the local server and the relay, but not the relay and the remote client

• the origin traffic may be encrypted or unencrypted

ngrok used to decrypt on their server, with an option to specify SSL certs manually they may have switched to full encryption since

If you want to know more about their workings, you may (or may not) find this other answer I wrote informative and digestible: https://stackoverflow.com/a/52614266/151312