localtunnel: Certificate has expired

hi, still no info 😦 if you need to you guys can use mine in the meanwhile, just connect to

-h https://tunnel.datahub.at

Having the same issue. @defunctzombie you could set up a button for donation in https://localtunnel.github.io/www/, I’m sure many of us will donate some money for this awesome tool

HEY HEY 😉

localtunnel.me is now up and running again 😉 i’m hosting it now.

also if you want to support it to not go down again, feel free to donate and support with the hosting fees 😉 Donation possible at https://localtunnel.me

Facing same issue. A workaround is to use -h http://localtunnel.me when initializing (notice http instead of https) and open http link instead of https in browser

@Pirngruber localtunnel.me seems have been down for several days now. Are you still running it?

I managed to get it working after adding -h http://localtunnel.me --local-https false

Hey everyone, I am now hosting localtunnel.me for this project so it should work like before. The only difference is that I’m handing out subdomains under the domain *.loca.lt instead of *.localtunnel.me (that’s because I don’t have full DNS control and without it can’t get a free wildcard cert for the domain without). Let me know if you run into any issues.

I am assuming the issue I am experiencing is related. Local tunnel hangs when trying to initialize.

do you still have those issues or is it stable now? Let me know @Pirngruber

Yesterday everything worked fine and the tunnel was being created. Today does not want to be created in any way. From the console just hangs without a response. The js-library returns the error " localtunnel server returned an error, please try again"

If i use lt -p 3001 -h http://localtunnel.me --local-https false i get the link, but my local server don’t show on the link, i’m getting the 502 Bad Gateway

Update: with options --local-https false it’s work. In cli i see label your url is: https://tamaelatedalmeida.localtunnel.me, but in browser https don’t work, http is fine

What can be wrong with certificates?

I‘ve just asked @defunctzombie on twitter if he wants me to host and maintain the localtunnel.me server… lets see

Is this place dead? my plugin is giving me tunnel server offline: unable to verify the first certificate, retry 1s I’d be happy to chip in for the certificate cost.

@przano

Localtunnel is running and waiting for new clients on port 443 of the domain localtunnel.me therefore there has to be a valid ssl-cert for localtunnel.me If a new client connects there, the server tells him the port (for example 4315) and a subdomain like abc.localtunnel.me so now the reverseproxy (nginx in our case) has to serve the correct ssl-cert for *.localtunnel.me and terminate the tls to let the https request of your browser connect to the correct port.

The wildcard (*.localtunnel.me) certificate was the problem.

And remember: it‘s not a problem if you’re not experienced right now, try to ask as much as you can and try things by yourself

soo @georgevlad42 & @przano everything should be up and running finally.

both names localtunnel.me & tunnel.datahub.at are up and have valid certs on all endpoints. the other problems like the 504 were because of the last updates which had to be done 😃

let me know if something doesn’t work like expected

Hi @defunctzombie , Is it possible to get the certificate updated?

thank you for your immediate assistance.

Thank you @Pirngruber https://github.com/localtunnel/localtunnel/issues/332#issuecomment-567226542

I am able to connect. Just for the information of users: custom server must be without a landing slash lt --host=https://tunnel.datahub.at not lt --host=https://tunnel.datahub.at/ 😉

-h http://localtunnel.me --local-https false --allow-invalid-cert true worked for me

@devjones Yes i am using the http in the url

/usr/bin/lt --port 4567 -h http://localtunnel.me --subdomain mydomain

this is the output I get your url is: https://mydomain.localtunnel.me

Seems to be still defaulting to https

@defunctzombie feel free to close this issue.

I can confirm that localtunnel domain is still not working but I’m using serverless domain and its working without problems. You can start tunnel on this domain by setting host to: https://serverless.social.

Example lt -s tunnel-test -p 5000 -h https://serverless.social

Since there still are some issues occuring, I’ll turn off the tunnel.datahub.at instance and focus on the localtunnel.me one

I think localtunnel/server is not designed for a multiinstance environment 😉

it still doesn’t work. is there any solution?

See comment

It looks like public localtunnel server is abandoned but it’s totally understandable: it costs money, requires efforts on maintenance and in the meantime generates no profit at all.

So I have a suggestion to everyone who uses it: please setup your own localtunnel server, it’s more or less easy and you won’t depend on @defunctzombie and limited bandwidth (public server was slow anyway). Localtunnel is absolutely great tool that helped me a lot in my job and I’m 100% sure it’s worth of 5$ on some VPS.

@Pirngruber you are the real mvp, thank you

@defunctzombie If you are not willing to renew the certificate, would be useful to be notified.

Thank you again. And sorry for the pressure.

Facing same issue. A workaround is to use -h http://localtunnel.me when initializing (notice http instead of https) and open http link instead of https in browser

Thank mybott. To anyone doing this, just make sure you’re not sending any sensitive data over localtunnel from a coffeeshop.