Nothing to worry about.

The portal loads some file via insecure connection. I forgot which file, but it's none of the communication with the server. Rather, some CSS file or something like it. I detected two of those and I reported them. One was fixed and I expect the other one resolved soon.

However, Chrome (and, probably, other browsers) will label a page as "insecure" the moment it does anything via non-encrypted channels, because the browser cannot determine if the data going that way is sensitive or not.