And here I am pretty much in the exact same time frame as the original case 
(2-3 days in) and I'm seeing the same issue again.  I can't download 
artifacts unless I remove my resource root url setting.

this the type of error I see in my logs.  the first is my actual first 
rejection...

Nov 05, 2021 8:49:15 AM FINE jenkins.security.ResourceDomainFilter doFilter 
Rejecting 
request to https://<root_resource_url>/login from xxx.xxx.xxxx.xxx on 
resource domain
Nov 05, 2021 9:03:58 AM FINE jenkins.security.ResourceDomainFilter doFilter 
Rejecting 
request to https:// <root_resource_url>  /login from xxx.xxx.xxxx.xxx   on 
resource domain  
Nov 05, 2021 09:04:17 AM FINE jenkins.security.ResourceDomainFilter 
doFilter Rejecting request to https://<root_resource_url>/instance-identity/ 
from xxx.xxx.xxxx.xxx on resource domain

I've combed through my logs around 8:49am time to see if there is any 
record of another event at that time.  Nothing really jumps out as being a 
problem.
I'm at a total loss right now.  No clue what is causing this issue.

On Wednesday, November 3, 2021 at 11:03:35 AM UTC-4 Matt Wilson wrote:

> I managed to get a service restart last night.  I just reapplied my 
> resource root url setting.
> mystery continues at this point.  After reapplying my settings, I can 
> download artifacts with no problem.  The logs are clean with respect to 
> these downloads, nothing out of the ordinary.
>
> when I reload my config page though I see an error below my resource url 
> just as before (see attached).  The stack trace is the same as before.
> I'm going to wait it out right now, but I'm expecting this will stop 
> working at somepoint over the next day or so.  I have no idea if this 
> "error" message was present before the upgrade to this version.
>
> On Tuesday, November 2, 2021 at 11:03:32 AM UTC-4 Matt Wilson wrote:
>
>> thanks.  Whats odd is that based on job log output this seemed to have 
>> been working for a few days, then "broke".  Right now I'm playing on 
>> scheduling a service restart.  Maybe I'll get lucky and its just a one 
>> off... I guy can dream.
>> On Tuesday, November 2, 2021 at 3:43:53 AM UTC-4 db...@cloudbees.com 
>> wrote:
>>
>>> On Tue, Nov 2, 2021 at 2:27 AM Matt Wilson <mwil...@gmail.com> wrote:
>>>
>>>>
>>>> Caused by: java.lang.NullPointerException
>>>>         at 
>>>> jenkins.security.ResourceDomainConfiguration.checkUrl(ResourceDomainConfiguration.java:174)
>>>>         at 
>>>> jenkins.security.ResourceDomainConfiguration.doCheckUrl(ResourceDomainConfiguration.java:88)
>>>>
>>>
>>> The URL responds with a 404 error message and has no response message 
>>> (of course error handling should be better). Would look at reverse proxy or 
>>> a nondefault web container as the likely culprit (I just checked 
>>> ci.jenkins.io to be sure it's not a general problem, and its resource 
>>> root URL works as expected).
>>>
>>> Another option might be problems with the instance-identity module I use 
>>> to determine URL correctness, but then the actual URLs should work, and 
>>> only form validation be broken.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/996eb23e-3993-40b7-9c26-bf24ee6b45cen%40googlegroups.com.

Reply via email to