ngrok
ngrok copied to clipboard
ERR_NGROK_354
starting from today, I'm getting this error.
ngrok http 3001 -subdomain=xxx.eu.ngrok.io
Failed to bind 'xxx.eu.ngrok.io.ngrok.io'. Nested subdomains of the ngrok base endpoint domain 'ngrok.io' are disallowed. Try 'xxx-eu-ngrok-io.ngrok.io' instead.
does anyone having same issue?
Hi.
Any kind of information and/or an ETA for a solution would be greatly appreciated. I'm on a paid plan and with this error I'm blocked from progressing in my work, so it's a serious problem for me.
Thanks in advance.
I've been using ngrok (on a paid plan) to tunnel frommy-subdomain.my-app.eu.ngrok.io for as long as Ive been subscribing. This change to ngrok has broken our testing and mobile development workflows too.
I've looked at the documentation and I believe this usage is classified as wildcard domains. I reckon this change is to force people to upgrade to the Business plan to use wildcard domains.
I reckon this change is to force people to upgrade to the Business plan to use wildcard domains.
If it's a mistake, fair enough. Hopefully we get a resolution fast. If it's an intentional change then that is shockingly bad service and they will lose customers.
Because my subdomains are all hardwired i've changed them from . to - and can now carry on. However, I agree that fixing a regression (if it is one) could have been handled better. For me, this is another reason to investigate https://github.com/beyondcode/expose
We use Ngork in our development setup and we faced this issue. We contacted their support team and they created permanent exceptions for our account to use nested domains. Their reply was very swift. If you can send an email to their support teams I am sure they'll help.
We are on the business plan and are having this issue as well.
Has there been any official communication on this?
The support team was able to enable nested subdomains on my account as well, but when I asked if this will work in perpetuity, they said it will not. This will only give a few months for us to figure it out.
We are looking forward to get this resolved ASAP, as our testing and production environments depends on it. Please keep us updated.
We were using nested subdomains to locally test the sharing capability of cookies with the Domain attribute.
Same issue. We use wildcard subdomains and need to test. Just sent ngrok an email.
ngrok start --all
Error message is: Nested subdomains of the ngrok base endpoint domain 'ngrok.io' are disallowed.
The proposed solution in that error message makes no sense
foo-bar-foorbar.com is not helpful when we need to give our customers a subdomain in the format foobar.foobar.com
Just following up on this and sorry for the lack of communication. The ngrok team doesn't actively monitor issues on this repo but we probably should.
We made a change to disallow "nested" subdomains of ngrok.io because we don't serve a valid TLS certificate for those DNS names, which was causing a lot of customer confusion.
For specific customers who depend on the old nested subdomain functionality, we do have a flag that we can switch on for your account if you send a quick email to [email protected] requesting the change.
Thank you for opening this issue! As of April 2016, the ngrok service has permanently moved to https://ngrok.com/. To join the community and file bug reports or feature enhancements for the ngrok agent, please go to https://github.com/ngrok/ngrok.
This repository is no longer actively maintained and will be archived soon to reduce confusion with the latest ngrok versions. We thank you for the continued support of ngrok and look forward to seeing you over at ngrok.com and the ngrok Community Repo.