Sorry, been offline and had some real work to do yesterday.Very simple setup. The Viasat router is on the desk not 2 feet away from my laptop and desktop. The desktop logs in to the router with no issues but running Win10. The Debian laptop is also not 2 feet away running Debian 11. Another Debian 10 machine logs in remotely with no issues. The Deb11 laptop brings up the status page with no log in necessary, but any other functions require a log in through any of the other pages, which are .asp pages.
I have a manually entered ip for the interface and a route entered directly to the router. I can get to the router but it doesn't allow all the functions. There no unusual configs and the whole system and setup works exactly as it should except for those pages accessed with Debian 11.
Angel, I'll try your suggestions for looking a the Chrome network stuff.I've read all the stuff up to 8:45am this morning (MST/MDT) and I'll check my config files for any unusual issues.
I didn't want to clog up the bandwidth and put all the info in the post. I was hoping for a response from anyone who had a similar issue and had a simple solution. I can get into the router and do what I need to do, so that's not a problem. I don't need to have access to my router via Debian 11.
So, the real issue is that I have Debian 11 on this laptop and and it's not behaving as it should, or behaving as my other Debian 10 machines, which access the pages with no issues. Just like to know why the new version doesn't behave like the old version.
thanks, TMSince anecdotes are making it into this thread, I'll submit one more, not really related to this issue. I frequent a number of automobile BBs where problems are presented and resolutions are offered. A not uncommon problem would be 'my car can't pass the smog test', and the fun begins. By the 50th post the list of recommended remedies would have the entire car replaced either in total or one part at a time, all probably due to a cracked, 2 dollar, 3mm vacuum hose, a simple solution.
On 8/27/22 22:51, tomas@tuxteam.de wrote:
On Sat, Aug 27, 2022 at 07:10:52PM -0400, Greg Wooledge wrote:On Sat, Aug 27, 2022 at 07:05:46PM -0400, Timothy M Butterworth wrote:On Sat, Aug 27, 2022 at 6:48 PM Greg Wooledge <greg@wooledge.org> wrote:On Sat, Aug 27, 2022 at 12:28:38PM -0600, tony mollica wrote:Yes, no problems accessing the .asp pages with Debian 10 and chrome.Both10 and 11 have the latest Chrome version.Wait, wait, wait, wait. I am *so* confused right now. Is the Debian system the WEB SERVER, or is it the WEB BROWSERThe Debian system is the web browser, a SOHO router is the server.So the problem is *not* "I have a .asp site and my web server stopped serving it properly", but rather "my browser is trying to hit a URL that happens to end with .asp and it's not working". Then all the focus on the 4 characters .asp in the URL are a complete red herring.Thanks, that was my point. I just couldn't express it so concisely :)What's the actual *symptom*? What does the web browser say or do when hitting this URL?Perhaps the 404 is coming in response to a subordinate resource (e.g. the Location: in a redirect or some other of the 3129 ways the Web has to play that game). That resource would depend on "the browser" in some general sense. Oh wait: does have the new installation a different /etc/hosts? Perhaps the OP has made an entry "back then" to get the router's cra^H^H^H Very Special GUI working? Something like that. Cheers