> When I connect using the Ingress route URL, I get the blank screen, but authentication is still fine.
This sounds like a problem with your etc/jolokia-access.xml configuration. How is it configured? If the problem was related to the HAWTIO_ROLES configuration I don't think it would work in any context, even locally. > It’s maybe worth noting that insecure connections are ok - when it’s “secured” it’s not. I'm not following you here? Can you elaborate? > I didn’t have this problem with 2.39 so Im wondering where to start looking ... I'd start with your etc/jolokia-access.xml. > ...can logging be increased for the interface? Are you talking about in the browser or on the broker? Justin 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 > >
