Hi Justin 

That indeed did resolve the problem!

Perhaps useful to include this in the upgrade notes.

Thank you very much!




> On 7 Apr 2025, at 22:53, Justin Bertram <jbert...@apache.org> wrote:
> 
> LET OP! Deze e-mail komt van buiten de organisatie. Klik niet op links en 
> open geen bijlagen tenzij je de afzender herkent en weet dat de inhoud veilig 
> is.
> 
> 
> 
> You may need to add <ignore-scheme/> to your etc/jolokia-access.xml. A PR
> [1] recently updated the upgrade documentation [2].
> 
> 
> Justin
> 
> [1] https://github.com/apache/activemq-artemis/pull/5612
> [2]
> https://activemq.apache.org/components/artemis/documentation/latest/versions.html#upgrading-from-2-39-0
> 
> On Mon, Apr 7, 2025 at 5:41 AM Kamara, George (RWS CIV)
> <george.kama...@rws.nl.invalid> wrote:
> 
>> Greetings.
>> 
>> Im upgrading to 2.40.0 - and have read the minor changes that are needed
>> for the upgrade (in this case HAWTIO_ROLE > ROLES), the instance itself
>> works fine.
>> 
>> I’ve deployed  in an environment to test and I’m not receiving the correct
>> role when using an external URL. The interface is blank with the HAWTIO
>> icon.
>> 
>> Im using K8s - When I port forward 8161 and connect to the UI using
>> localhost:8161, The role is correct, authentication is accepted and I can
>> see everything.
>> When I connect using the Ingress route URL, I get the blank screen, but
>> authentication is still fine.
>> 
>> It’s maybe worth noting that insecure connections are ok - when it’s
>> “secured” it’s not.
>> 
>> I didn’t have this problem with 2.39 so Im wondering where to start
>> looking - can logging be increased for the interface?
>> 
>> Thanks in advance
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
>> For additional commands, e-mail: users-h...@activemq.apache.org
>> For further information, visit: https://activemq.apache.org/contact
>> 
>> 

Reply via email to