Edge keeps adding local IP to TabProcConfig thus page doesn't load.

Confirmed Issue #16722404 • Assigned to Venkat K.

Details

Author
Jakub
Created
Apr 3, 2018
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 5 people

Sign in to watch or report this issue.

Steps to reproduce

Whenever I set start pages in my Edge which begin with local IP like 192.168.1.100 or load such a page which doesn’t exist (returns 404) then local IP 192.168.1.100 gets added to Komputer\HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge\TabProcConfig and it is no longer possible to load any pages which begin with 192.168.1.100 (even existing ones).

I have to manually edit the registry almost every time if I want to use local IPs what is pretty annoying.

Is this a bug or something can be set in Edge to prevent that? I have searched the Internet but haven’t found any explanation or solution but only this manual work around with editing the registry.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Arvind M.”

      Changed Assigned To from “Arvind M.” to “Ali A.”

    • Thank you for filing this bug, Jakub. Can you please tell me what version of Windows and Edge you are running? Are you able to file a Feedback Hub issue so that we can better understand what might be causing the issue you’re experiencing? Ideally, we would need a trace of when you try loading the page.

    • Windows and Edge version:
      Windows 10 Home
      Version 1803
      Build No. 17134.48

      Egde Version:
      Microsoft Edge 42.17134.1.0
      Microsoft EdgeHTML 17.17134

      I don’t know what Feedback Hub is but I can describe the problem more clearly:

      1. I have Tomcat instance running on my Windows 10. It is fired manually and not as a service
      2. On that Tomcat server I have HTML page which I can access through browser.
      3. My local network IP and port are: 192.168.1.100:8080 so I can access my pages using e.g. http://192.168.1.100:8080/some-page.html
      4. If my Tomcat is down and I load the existing page http://192.168.1.100:8080/some-page.html or if Tomcat is running but I want to access non-existing page e.g. http://192.168.1.100:8080/no-such-page.html then IP 192.168.1.100 gets added to Komputer\HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge\TabProcConfig and even if Tomcat is up and I want to load existing page I won’t be able to connect to that page.

      It looks like Edge is rejecting that connection and I have to manually edit the registry to be able to load http://192.168.1.100:8080/some-page.html again.

      It is enough to either load non-existing page or load existing page when tomcat is down and Edge is blocking you to access http://192.168.1.100:8080/ from now on.

    • Just to clarify point 4.

      I should have written instead of:

      “and even if Tomcat is up and I want to load existing page I won’t be able to connect to that page.”

      this:

      and even if I later turn Tomcat on and load existing page I won’t be able to connect to that page ever again.

    • Microsoft Edge Team

      Changed Status to “Needs root cause”

      Changed Status from “Needs root cause” to “Confirmed”

      Changed Assigned To from “Ali A.” to “Venkat K.”

    • I try to login to my Router, NAS or IP camera by IP and nothing happens within Edge go to TabProcConfig and the IPs are there. Nothing gets me to an IP in Edge. I can get to the IPs in IE 11 and Chrome. Windows 10 Version 1803 build 17134.285. On my other computer with Edge same build I can. It’s something within Edge on MY computer is preventing me to enter and IP 192.168.1.1, etc. Would love a fix or work around for Edge or I’ll never use EDGE. I guess Chrome will become my browser of choice as more and more web pages are no longer being supported by IE 11.

    You need to sign in to your Microsoft account to add a comment.

    Sign in