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 a month ago. No joy.
Anyone reading this have an input with those guys to hurry up and fix this?
Many thanks, -T
On Sun, 30 Sep 2018 17:00:12 -0700 ToddAndMargo ToddAndMargo@zoho.com 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 not been accepting new bugs for over a month. I eMailed the support address a month ago. No joy.
Anyone reading this have an input with those guys to hurry up and fix this?
There are lots of bugs opened within the last month. Do a search on systemd, and sort on ID to put latest first. There was a bug opened today. Even I have opened a bug in the last month. I don't know what error 500 is, but I think you should try creating a new bugzilla logon. The one you are using must have something wrong with it.
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 bugzilla logon. The one you are using must have something wrong with it.
It's an error within the webserver that's hosting the service (the text explains that, the code number lets you check on the error type if the supplied text isn't useful).
This usually means a webserver configuration error, or an error in a program that generates something for the webserver. But *can* be due to data that your browser is supplying to the webserver, though that suggests careless programming on the webserver that a browser can make it fail so spectacularly (the program should handle all data, including erroneous data, without pranging the webserver).
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 users@lists.fedoraproject.org wrote:
It's an error within the webserver that's hosting the service (the text explains that, the code number lets you check on the error type if the supplied text isn't useful).
This usually means a webserver configuration error, or an error in a program that generates something for the webserver. But *can* be due to data that your browser is supplying to the webserver, though that suggests careless programming on the webserver that a browser can make it fail so spectacularly (the program should handle all data, including erroneous data, without pranging the webserver).
Thanks.
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 should try creating a new bugzilla logon. The one you are using must have something wrong with it.
It's an error within the webserver that's hosting the service (the text explains that, the code number lets you check on the error type if the supplied text isn't useful).
This usually means a webserver configuration error, or an error in a program that generates something for the webserver. But *can* be due to data that your browser is supplying to the webserver, though that suggests careless programming on the webserver that a browser can make it fail so spectacularly (the program should handle all data, including erroneous data, without pranging the webserver).
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?
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. The only IP address that bugzilla.redhat.com seems to resolve to is 209.132.183.69.
And, while not ideal, you could create a new account using a gmail or other free email account.
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 cache?
Yes
I doubt changing WAN IP would make a difference. The only IP address that bugzilla.redhat.com seems to resolve to is 209.132.183.69.
My WAN IP, Not theirs.
And, while not ideal, you could create a new account using a gmail or other free email account.
That will be my next step.
Thank you!
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 different browser?
Firefox and Brave
Have you cleared your cache?
Yes
I doubt changing WAN IP would make a difference. The only IP address that bugzilla.redhat.com seems to resolve to is 209.132.183.69.
My WAN IP, Not theirs.
I understood. But you're still only going to arrive at the same destination.
And, while not ideal, you could create a new account using a gmail or other free email account.
That will be my next step.
Sounds good.
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 guessing.
I am not at all familiar with the infrastructure of Red Hat. But, it would seem to be a rather complicated way to set things up that way unless there are regional content restrictions. Like what services such as Netflix would need to do.
How many servers are you guessing are in the farm that are responsible for running Bugzilla? It would seem to me to have to be quite a large number such that only a few (one) account would be affected such that it would not be noticed by others.
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 location or previous visits. I am guessing.
I am not at all familiar with the infrastructure of Red Hat. But, it would seem to be a rather complicated way to set things up that way unless there are regional content restrictions. Like what services such as Netflix would need to do.
How many servers are you guessing are in the farm that are responsible for running Bugzilla? It would seem to me to have to be quite a large number such that only a few (one) account would be affected such that it would not be noticed by others.
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
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 routing traffic bases on geographic location or previous visits. I am guessing.
I am not at all familiar with the infrastructure of Red Hat. But, it would seem to be a rather complicated way to set things up that way unless there are regional content restrictions. Like what services such as Netflix would need to do.
How many servers are you guessing are in the farm that are responsible for running Bugzilla? It would seem to me to have to be quite a large number such that only a few (one) account would be affected such that it would not be noticed by others.
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
Tried creating a different account with a different eMail address and that did not work either
:'(
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 issues?
Possible to try using a mobile phone to eliminate an ISP issue? Or if you're using a laptop, move to a Free WiFi hotspot?
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.
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, 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:
Red Hat Bugzilla – Log in to Red Hat Bugzilla
Home | New | Search |
[?] | Reports | Requests | New Account
Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Red Hat Bugzilla needs a legitimate login and password to continue. Login: Password:
(Note: you should make sure cookies are enabled for this site. Otherwise, you will be required to log in frequently.)
If you don't have a Red Hat Bugzilla account, you can create a new account. A user account is required to file a new bug or to comment into existing ones so that you can be contacted if more information is needed. If you have an account, but have forgotten your password, enter your login name below and submit a request to change your password.
Home | New | Search |
[?] | Reports | Requests | New Account | Report Bugzilla Bug
Legal
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_DENIED
I see, in Firefox:
Red Hat Bugzilla – Log in to Red Hat Bugzilla
Home | New | Search | [?] | Reports | Requests | New Account
Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Red Hat Bugzilla needs a legitimate login and password to continue. Login: Password:
(Note: you should make sure cookies are enabled for this site. Otherwise, you will be required to log in frequently.)
If you don't have a Red Hat Bugzilla account, you can create a new account. A user account is required to file a new bug or to comment into existing ones so that you can be contacted if more information is needed. If you have an account, but have forgotten your password, enter your login name below and submit a request to change your password.
Home | New | Search | [?] | Reports | Requests | New Account | Report Bugzilla Bug Legal
Looks like exactly what I get. I have two accounts. Both have the same issue in both Firefox and Brave
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 IP (erroneously?) might change while trying to enter bugzilla with your credentials, this might explain the issue. I'd try to make sure to keep the same WAN IP during the whole login procedure.
HTH
Good luck, Wolfgang
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 WAN IPs, but if that - after a quick search - means, that your WAN IP (erroneously?) might change while trying to enter bugzilla with your credentials, this might explain the issue. I'd try to make sure to keep the same WAN IP during the whole login procedure.
.. or better: making sure your WAN IP stays the same while submitting a bug.
Sorry Wolfgang
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 floating WAN IP?
I'm not familiar with floating WAN IPs, but if that - after a quick search - means, that your WAN IP (erroneously?) might change while trying to enter bugzilla with your credentials, this might explain the issue. I'd try to make sure to keep the same WAN IP during the whole login procedure.
.. or better: making sure your WAN IP stays the same while submitting a bug.
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 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 would get a 4xx result saying you're not allowed. A 5xx result is bad. If it's still happening, have you contacted the infrastructure people? They would be able to check the logs and find out what's going on.
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 either not respond at all or you would get a 4xx result saying you're not allowed. A 5xx result is bad. If it's still happening, have you contacted the infrastructure people? They would be able to check the logs and find out what's going on.
And to further this, the address to send such queries should be bugzilla-owner@redhat.com.
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 filtering though. It would either not respond at all or you would get a 4xx result saying you're not allowed. A 5xx result is bad. If it's still happening, have you contacted the infrastructure people? They would be able to check the logs and find out what's going on.
And to further this, the address to send such queries should be bugzilla-owner@redhat.com.
That is who ignored me.
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.
That's not a result you should get from filtering though. It would either not respond at all or you would get a 4xx result saying you're not allowed. A 5xx result is bad. If it's still happening, have you contacted the infrastructure people? They would be able to check the logs and find out what's going on.
And to further this, the address to send such queries should be bugzilla-owner@redhat.com.
That is who ignored me.
I wrote them again
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 accepting new bugs for over a month. I eMailed the support address a month ago. No joy.
Anyone reading this have an input with those guys to hurry up and fix this?
I submitted a BZ on 9/12/18 with no problem. https://bugzilla.redhat.com/show_bug.cgi?id=1627963
And picking a random higher number...
https://bugzilla.redhat.com/show_bug.cgi?id=1632222%C2%A0%C2%A0 was Reported: 2018-09-24 07:59.
So, maybe it isn't a problem on red hat's end?
Clear the cache in your browser? Try a different browser? Create a new account?
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
Bugzilla has not been accepting new bugs for over a month. I eMailed the support address a month ago. No joy.
Anyone reading this have an input with those guys to hurry up and fix this?
I submitted a BZ on 9/12/18 with no problem. https://bugzilla.redhat.com/show_bug.cgi?id=1627963
And picking a random higher number...
https://bugzilla.redhat.com/show_bug.cgi?id=1632222%C2%A0%C2%A0 was Reported: 2018-09-24 07:59.
So, maybe it isn't a problem on red hat's end?
Clear the cache in your browser? Try a different browser? Create a new account?
Hmmmm. Good to know it is at my end. That I can fix.
Thank you!