Cloudflare tunnels and ASP.NET Core Blazor website showing 404 - Stack Overflow

admin管理员组

文章数量:1124693

I have been playing around with Blazor + Mudblazor. I have an ASP.NET Core hosted Blazor website. I can host it on my own network and connect to it on:

http://192.168.86.116:8084/

I want to share it on the public internet like I have other of my stuff: , and

First one is static nginx website hosted. API is an ASP.NET Core Web API. Client is a static Blazor wasm website. They are all running locally on my machine.

The new Blazor web app I am trying to deploy and show is but it just returns 404 not found.

My cloudflare tunnels is setup entirely the same. My new service is deployed entirely the same way as the others, but for some reason it's never found through the tunnel. I feel like it's like something small stupid thing I am missing.

I can run my docker image locally. I can run it on my local network server and browse to it. But when I try to connect through the tunnel I just get not found. I tried changing the public hostname to and other just to see if there was some caching.

The template for creating my new Blazor website was:

dotnet new mudblazor --interactivity WebAssembly --name HelpMotivateMe --all-interactive

if that helps.

I am running it like I do the other projects:

docker run -d -p 8084:8080 --name helpmotivateme --network my-custom-network kiksen1987/helpmotivateme:1.0.1

And my ASP.NET Core Web API is run like the following:

docker run -d -p 8081:8080 --name myapp --network my-custom-network kiksen1987/pi:1.0.4

Dockerfiles are pretty similar, but can't see the error being in them, since I am able to run them and see them locally and on my local network server.

I have been playing around with Blazor + Mudblazor. I have an ASP.NET Core hosted Blazor website. I can host it on my own network and connect to it on:

http://192.168.86.116:8084/

I want to share it on the public internet like I have other of my stuff: https://topswagcode.dev, https://api.topswagcode.dev and https://client.topswagcode.com

First one is static nginx website hosted. API is an ASP.NET Core Web API. Client is a static Blazor wasm website. They are all running locally on my machine.

The new Blazor web app I am trying to deploy and show is https://test.topswagcode.dev but it just returns 404 not found.

My cloudflare tunnels is setup entirely the same. My new service is deployed entirely the same way as the others, but for some reason it's never found through the tunnel. I feel like it's like something small stupid thing I am missing.

I can run my docker image locally. I can run it on my local network server and browse to it. But when I try to connect through the tunnel I just get not found. I tried changing the public hostname to https://help.topswagcode.dev and other just to see if there was some caching.

The template for creating my new Blazor website was:

dotnet new mudblazor --interactivity WebAssembly --name HelpMotivateMe --all-interactive

if that helps.

I am running it like I do the other projects:

docker run -d -p 8084:8080 --name helpmotivateme --network my-custom-network kiksen1987/helpmotivateme:1.0.1

And my ASP.NET Core Web API is run like the following:

docker run -d -p 8081:8080 --name myapp --network my-custom-network kiksen1987/pi:1.0.4

Dockerfiles are pretty similar, but can't see the error being in them, since I am able to run them and see them locally and on my local network server.

• asp.net-core
• blazor
• asp.net-core-webapi
• cloudflare
• mudblazor

Share Improve this question Follow edited 2 days ago marc_s 754k183183 gold badges1.4k1.4k silver badges1.5k1.5k bronze badges asked 2 days ago KiksenKiksen 1,76722 gold badges2121 silver badges4646 bronze badges

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

well https://test.topswagcode.dev/ is up and running now through cloudflare tunnels. I shutdown my tunnel and started it again. I tried to create a new Hostname for one of my other working services and saw it also didn't work. Eg. https://lala.topswagcode.dev pointing to same as https://api.topswagcode.dev

Since the new "lala" subdomain didn't work, it seemed all new subdomains wasn't working for some reason. Cloudflare logs didn't show anything else than "not found" and my local tunnel container also didn't show anything. My guess is configuration sync stopped working at some point and only worked with already existing routes.

After killing container and spinning new up both lala and test subdomain worked again.

I really would have loved any kind of debug information that sync had stopped or any kind of warnings.

本文标签： Cloudflare tunnels and ASPNET Core Blazor website showing 404Stack Overflow