On 10/2/18 7:45 PM, ToddAndMargo wrote:
On 10/2/18 5:18 PM, Todd Zullinger wrote:
Samuel Sieb wrote:
On 10/2/18 3:32 PM, ToddAndMargo wrote:
The WAN IP (DHCP) has been the same for months (auto renewal).
I was just wondering if bugzilla had that particular IP range
filtered for some reason.
On 10/2/18 5:18 PM, Todd Zullinger wrote:
Samuel Sieb wrote:
On 10/2/18 3:32 PM, ToddAndMargo wrote:
The WAN IP (DHCP) has been the same for months (auto renewal).
I was just wondering if bugzilla had that particular IP range
filtered for some reason.
That's not a result you should get from f
On 10/2/18 3:36 PM, Samuel Sieb wrote:
If it's still happening, have you contacted the infrastructure people?
I did. They ignored me.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproj
On 10/2/18 6:16 PM, Tim via users wrote:
Allegedly, on or about 2 October 2018, ToddAndMargo sent:
The error with Brave:
This site can’t be reached
The webpage at https://bugzilla.redhat.com/post_bug.cgi might be
temporarily down or it may have moved permanently to a new web
address.
ERR_ACCESS
Allegedly, on or about 2 October 2018, ToddAndMargo sent:
> The error with Brave:
>
> This site can’t be reached
> The webpage at https://bugzilla.redhat.com/post_bug.cgi might be
> temporarily down or it may have moved permanently to a new web
> address.
> ERR_ACCESS_DENIED
I see, in Firefox:
Samuel Sieb wrote:
> On 10/2/18 3:32 PM, ToddAndMargo wrote:
>> The WAN IP (DHCP) has been the same for months (auto renewal).
>> I was just wondering if bugzilla had that particular IP range
>> filtered for some reason.
>
> That's not a result you should get from filtering though. It would eithe
On 10/2/18 3:32 PM, ToddAndMargo wrote:
The WAN IP (DHCP) has been the same for months (auto renewal).
I was just wondering if bugzilla had that particular IP range
filtered for some reason.
That's not a result you should get from filtering though. It would
either not respond at all or you wo
On 10/2/18 5:34 AM, Wolfgang Pfeiffer wrote:
On Tue, Oct 02, 2018 at 02:30:10PM +0200, Wolfgang Pfeiffer wrote:
On Mon, Oct 01, 2018 at 06:52:56PM -0700, ToddAndMargo wrote:
Any good work arounds? Maybe I am unlucky to get the one
mis-configured server on the server farm? Maybe change my
flo
On 10/3/18 1:47 AM, Tim via users wrote:
> Allegedly, on or about 2 October 2018, Ed Greshko sent:
>> Could it be your ISP has a transparent proxy causing issues?
> I had wondered that, too. But a HTTPS connection ought to put a stop
> to that kind of ISP shenanigans.
>
Hmmm Good point.
--
Allegedly, on or about 2 October 2018, Ed Greshko sent:
> Could it be your ISP has a transparent proxy causing issues?
I had wondered that, too. But a HTTPS connection ought to put a stop
to that kind of ISP shenanigans.
--
[tim@localhost ~]$ uname -rsvp
Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue
On Tue, Oct 02, 2018 at 02:30:10PM +0200, Wolfgang Pfeiffer wrote:
On Mon, Oct 01, 2018 at 06:52:56PM -0700, ToddAndMargo wrote:
Any good work arounds? Maybe I am unlucky to get the one
mis-configured server on the server farm? Maybe change my
floating WAN IP?
I'm not familiar with floating
On Mon, Oct 01, 2018 at 06:52:56PM -0700, ToddAndMargo wrote:
Any good work arounds? Maybe I am unlucky to get the one
mis-configured server on the server farm? Maybe change my
floating WAN IP?
I'm not familiar with floating WAN IPs, but if that - after a quick
search - means, that your WAN
On 10/2/18 6:24 PM, ToddAndMargo wrote:
>
>
> Tried creating a different account with a different eMail address and
> that did not work either
Just created a new account with my gmail address using "brave". Worked fine
from
here in Taiwan.
Could it be your ISP has a transparent proxy causing i
On 10/2/18 3:14 AM, ToddAndMargo wrote:
On 10/2/18 12:35 AM, Ed Greshko wrote:
On 10/2/18 2:00 PM, ToddAndMargo wrote:
On 10/1/18 9:45 PM, Ed Greshko wrote:
I understood. But you're still only going to arrive at the same
destination.
That same destination is a server farm. They may be r
On 10/2/18 12:35 AM, Ed Greshko wrote:
On 10/2/18 2:00 PM, ToddAndMargo wrote:
On 10/1/18 9:45 PM, Ed Greshko wrote:
I understood. But you're still only going to arrive at the same destination.
That same destination is a server farm. They may be routing
traffic bases on geographic locatio
On 10/2/18 2:00 PM, ToddAndMargo wrote:
> On 10/1/18 9:45 PM, Ed Greshko wrote:
>> I understood. But you're still only going to arrive at the same destination.
>>
>
>
> That same destination is a server farm. They may be routing
> traffic bases on geographic location or previous visits.
> I am gu
On 10/1/18 9:45 PM, Ed Greshko wrote:
I understood. But you're still only going to arrive at the same destination.
That same destination is a server farm. They may be routing
traffic bases on geographic location or previous visits.
I am guessing.
___
On 10/2/18 12:21 PM, ToddAndMargo wrote:
> On 10/1/18 7:05 PM, Ed Greshko wrote:
>> On 10/2/18 9:52 AM, ToddAndMargo wrote:
>>>
>>> Any good work arounds? Maybe I am unlucky to get the one
>>> mis-configured server on the server farm? Maybe change my
>>> floating WAN IP?
>>
>> Have you tried a di
On 10/1/18 7:05 PM, Ed Greshko wrote:
On 10/2/18 9:52 AM, ToddAndMargo wrote:
Any good work arounds? Maybe I am unlucky to get the one
mis-configured server on the server farm? Maybe change my
floating WAN IP?
Have you tried a different browser?
Firefox and Brave
Have you cleared your
On 10/2/18 9:52 AM, ToddAndMargo wrote:
>
> Any good work arounds? Maybe I am unlucky to get the one
> mis-configured server on the server farm? Maybe change my
> floating WAN IP?
Have you tried a different browser? Have you cleared your cache?
I doubt changing WAN IP would make a difference.
On 10/1/18 9:39 AM, Tim via users wrote:
ToddAndMargo:
When I press "Submit" on a new bug, I get:
Internal Server Error
The server encountered an internal error and was unable to
complete your request.
Error 500
stan:
I don't know what error 500 is, but I think you shoul
> ToddAndMargo:
> >> The server encountered an internal error and was unable to
> >> complete your request.
> >> Error 500
> stan:
> > I don't know what error 500 is
On Tue, 02 Oct 2018 02:09:12 +0930
Tim via users wrote:
> It's an error within the webserver that's hosting the s
ToddAndMargo:
>> When I press "Submit" on a new bug, I get:
>>
>> Internal Server Error
>>
>> The server encountered an internal error and was unable to
>> complete your request.
>> Error 500
stan:
> I don't know what error 500 is, but I think you should try creating
> a new bugzil
On 9/30/18 5:50 PM, Ed Greshko wrote:
On 10/1/18 8:00 AM, ToddAndMargo wrote:
Hi All,
When I press "Submit" on a new bug, I get:
Internal Server Error
The server encountered an internal error and was unable to
complete your request.
Error 500
bugzilla.redhat.com
Bug
On 10/1/18 8:00 AM, ToddAndMargo wrote:
> Hi All,
>
> When I press "Submit" on a new bug, I get:
>
> Internal Server Error
>
> The server encountered an internal error and was unable to
> complete your request.
> Error 500
>
> bugzilla.redhat.com
>
> Bugzilla has not been accept
On Sun, 30 Sep 2018 17:00:12 -0700
ToddAndMargo wrote:
> When I press "Submit" on a new bug, I get:
>
> Internal Server Error
>
> The server encountered an internal error and was unable to
> complete your request.
> Error 500
>
> bugzilla.redhat.com
>
> Bugzilla has n
Hi All,
When I press "Submit" on a new bug, I get:
Internal Server Error
The server encountered an internal error and was unable to
complete your request.
Error 500
bugzilla.redhat.com
Bugzilla has not been accepting new bugs for over a month.
I eMailed the support address
27 matches
Mail list logo
