Re: Newly installed roundup 2.2.0. roundup-demo timeout errors

"John P. Rouillard" <[email protected]> Wed, 10 Aug 2022 14:46:42 -0400
Newsgroups	gmane.comp.bug-tracking.roundup.user
Message-ID	<[email protected]>
Hi Ed:

In message <[email protected]>,
=?UTF-8?Q?Martin_=c3=96stlund?= via Roundup-users writes:
>On 8/10/22 14:30, Ed Trumbull wrote:
>> I should add the browser error:
>> "
>> The connection was reset
>> 
>> The connection to the server was reset while the page was loading.
>> 
>> The site could be temporarily unavailable or too busy. Try again in a 
>> few moments.
>> If you are unable to load any pages, check your computer's network 
>> connection.
>> If your computer or network is protected by a firewall or proxy, make 
>> sure that Firefox is permitted to access the web.
>> "
>> 
>> I have verified that I can access other web sites with no problems from 
>> this browser within this VM.
>
>In Ubuntu 22.04, the firefox browser is installed as a snap package, 
>basically meaning it is run in a sort of containerized environment on 
>your machine, and it is therefore somewhat restricted in what it can do.
>
>I'm not sure if this is the reason it doesn't work for you, but as a 
>troubleshooting step, could you try to install a different browser ?
>Preferable manual downloading, i.e. chrome, since apt seems to prefer to 
>install snap packages now a days

Nice idea Martin.

Another way to test is to open a terminal. In the terminal type:

  telnet localhost 8917

you should see:

  Trying 127.0.0.1...
  Connected to localhost.
  Escape character is '^]'.

type

  GET /demo/


That's two returns/enters so there is a blank line. You should see:

   <!--
   This is the default body that is displayed when people visit the
   tracker. The tag below lists the currently open issues. You may
   replace it with a greeting message, or a different list of issues or
   whatever. It's a good idea to have the issues on the front page though
   -->
   <!DOCTYPE html>
   <html>
   [plus more stuff ...]

followed by the rest of the page. If you don't have telnet installed
you might have netcat istalled and you can use:

  nc localhost 8917

and just type the "GET /demo/" and you should see the same output.

If you use 'GET /foo/' (remember to follow with two returns) instead
you should see:

   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
        "http://www.w3.org/TR/html4/strict.dtd">
   <html>
    <head>
        <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
        <title>Error response</title>
    </head>
    <body>
        <h1>Error response</h1>
        <p>Error code: 404</p>
        <p>Message: /foo/.</p>
        <p>Error code explanation: 404 - Nothing matches the given URI.</p>
    </body>
   </html>

also you can use:

   curl -v http://localhost:8917/demo/

and you should see some output that incudes:

  < HTTP/1.1 200 OK
  < Server: BaseHTTP/0.6 Python/3.6.9

near the top of the output.

If these all work, then something is wrong with the browser. In my
test I used firefox installed as an actual package and not a snap.

Have a great day.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.