Your package doesn't work at all :( Just wasted my time :(
You can use my fork where I've fixed a lot of things.
https://github.com/ffMathy/FluffySpoon.Ngrok
@ffMathy how do we utilize an ngrok auth token? I am passing my authToken from config (appsettings.json) to the "options" in my program.cs file.
builder.Services.AddNgrokHostedService(new FluffySpoon.Ngrok.NgrokOptions() { AuthToken = builder.Configuration.GetValue<string>("ngrokAuthToken") });
I have your fork working, but am getting a generic error:
Before you can serve HTML content, you must sign up for an ngrok account and install your authtoken. (ERR_NGROK_6022)
@CoreySchneider-MSFT I will check that out and get it fixed this weekend, ASAP!
In the meanwhile, can you open a dedicated issue for that particular issue over at my repo? If not, I'll do it for you in the weekend, but it'd be easier if you could help out with that.
@ffMathy thank you for prompt response, I was able to get working by running ngrok.exe from my project folder manually in powershell and setting the authtoken:
Ex: ".\ngrok.exe authtoken token_value"
however, the tunnel times out when attempting to browse the ngrok url.
I am unable to open an issue on your repo, I do not see the "Issues" link.

FYI: I am trying to do this in a BlazorServer aspnetcore 6.0 app.
What the... Oh wow, issues are disabled? That's so strange... I never do that. Perhaps it's because it's a fork or something. Will enable that soon.
Yeah I think there is a regression somewhere. I am most likely just forgetting to pass the Auth token to the executable.
I recently did a rewrite to allow for more testability and better integration tests. Ironically I don't think I had a test that checked if Auth tokens were still working 😒
Of course that's not acceptable, and I'll have it fixed and stabilized very soon.
Will also enable issues in the other repo.
Issues have now been enabled for the project.
I'll keep you posted on progress.
It has now been resolved!
See more details here: https://github.com/ffMathy/FluffySpoon.Ngrok/issues/61
I also updated the package to support the Options pattern better.
@CoreySchneider-MSFT did the change work for you? :pray: