Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to the Power Users community on Codidact!

Power Users is a Q&A site for questions about the usage of computer software and hardware. We are still a small site and would like to grow, so please consider joining our community. We are looking forward to your questions and answers; they are the building blocks of a repository of knowledge we are building together.

Post History

66%
+2 −0
Q&A net::ERR_HTTP2_PROTOCOL_ERROR for a single user when using an Angular + ASP.NET Core application

Note: I am posting this here because I think this is more related to some configuration issue rather than a programming problem I have deployed an Angular (SPA) + ASP.NET Core application in a k8s...

0 answers  ·  posted 1y ago by Alexei‭  ·  edited 1y ago by Alexei‭

#2: Post edited by user avatar Alexei‭ · 2023-07-03T08:07:57Z (over 1 year ago)
added more details
  • Note: I am posting this here because I think this is more related to some configuration issue rather than a programming problem
  • I have deployed an Angular (SPA) + ASP.NET Core application in a k8s cluster and it works fine for all the users so far (devs, testers, internal clients). However, for a single colleague, the SPA is unable to fetch API resources due to the following errors:
  • > Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR
  • >
  • > Failed to load resource: net::ERR_CONNECTION_CLOSED
  • Note: the same application works fine for that user when deployed in IIS.
  • My colleague is using Windows 10.
  • Things I have tried:
  • - change browsers: the same happens in Firefox, Chrome and Edge Chromium
  • - tried to disable HTTP2 in the ASP.NET Core 2. Chrome Developer tools still reports h2 (HTTP2) connections and this might be caused by the fact that an nginx is handling connections between the SPA and the API running in the pod
  • - allowed remote access for the user on two different servers and try to access the site from there. This rules out possible Windows configuration issues on his own machine. The site works normally for all others when trying from these remote machines.
  • I am left with no clues about what might be the cause. My only guess would be that it is somehow linked to a profile misconfiguration which is replicated when the user logs in using the same profile in another machine.
  • Any ideas about what to try?
  • Note: I am posting this here because I think this is more related to some configuration issue rather than a programming problem
  • I have deployed an Angular (SPA) + ASP.NET Core application in a k8s cluster and it works fine for all the users so far (devs, testers, internal clients). However, for a single colleague, the SPA is unable to fetch API resources due to the following errors:
  • > Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR
  • >
  • > Failed to load resource: net::ERR_CONNECTION_CLOSED
  • Note: the same application works fine for that user when deployed in IIS.
  • My colleague is using Windows 10.
  • Things I have tried:
  • - change browsers: the same happens in Firefox, Chrome and Edge Chromium
  • - tried Incognito / InPrivate
  • - tried to disable HTTP2 in the ASP.NET Core 2. Chrome Developer tools still reports h2 (HTTP2) connections and this might be caused by the fact that an nginx is handling connections between the SPA and the API running in the pod
  • - allowed remote access for the user on two different servers and try to access the site from there. This rules out possible Windows configuration issues on his own machine. The site works normally for all others when trying from these remote machines.
  • I am left with no clues about what might be the cause. My only guess would be that it is somehow linked to a profile misconfiguration which is replicated when the user logs in using the same profile in another machine.
  • Any ideas about what to try?
  • ----
  • Just discussed it with that colleague and the problem no longer occurs. There is a chance that the VPN (Cisco AnyConnect) interfered with this, as the person works both in the office (no VPN) and from home (VPN required). The problem seems to be disappeared after trying Incognito and VPN active, but we try to reproduce it again to fully understand the cause.
#1: Initial revision by user avatar Alexei‭ · 2023-07-03T06:45:14Z (over 1 year ago)
net::ERR_HTTP2_PROTOCOL_ERROR for a single user when using an Angular + ASP.NET Core application
Note: I am posting this here because I think this is more related to some configuration issue rather than a programming problem

I have deployed an Angular (SPA) + ASP.NET Core application in a k8s cluster and it works fine for all the users so far (devs, testers, internal clients). However, for a single colleague, the SPA is unable to fetch API resources due to the following errors:


 > Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR
 > 
 > Failed to load resource: net::ERR_CONNECTION_CLOSED

Note: the same application works fine for that user when deployed in IIS.

My colleague is using Windows 10.

Things I have tried:

- change browsers: the same happens in Firefox, Chrome and Edge Chromium
- tried to disable HTTP2 in the ASP.NET Core 2. Chrome Developer tools still reports h2 (HTTP2) connections and this might be caused by the fact that an nginx is handling connections between the SPA and the API running in the pod
- allowed remote access for the user on two different servers and try to access the site from there. This rules out possible Windows configuration issues on his own machine. The site works normally for all others when trying from these remote machines.

I am left with no clues about what might be the cause. My only guess would be that it is somehow linked to a profile misconfiguration which is replicated when the user logs in using the same profile in another machine.

Any ideas about what to try?