Hi again Marius. The last solution you gave me is working fine. Haven't see any warning or connections that are out of SSL so far when configuring the server over the web interface. But today I found something different if I want to manage the server over the API:
If you go to *System/Node > Nodes* and hover the pointer over the *API Browser* button, I can see that it points to the Internal IP *10.X.X.X (*http://10.X.X.X:12900/api-browser) with HTTP protocol. If you click on it you won't got anywhere (of course there is no way the browser finds a valid route to the server). But if I replace the internal IP address with the external, I will be able to surf the api-browser web page. It even display a popup window with the following warning: IMPORTANT: Please use the configured REST transport address > (http://10.X.X.X:12900) if you want working examples. This connection to > http://192.168.0.162:12900 will cause problems with > Access-Control-Allow-Origin. Any how, regarles de last message, I was able to use the API without encryption to create a roll with the curl example found in documentation <http://docs.graylog.org/en/2.0/pages/users_and_roles/system_users.html?highlight=rest#creating-the-role> . Shouldn't be this API access also be part of *graylog-ctl enforce-ssl* command? Thank you in advance. Pasqual T. -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/df0a88fb-7858-4fb7-9358-be971e13453b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
