I'm running the VMware OVA. I've tried every combination of http/https and eth0's IP and FQDN I can think of. Some changes "get a little further", like when I change rest_transport_uri to https with the IP or FQDN--this at least pulls up the login page, but ends up failing with the same error after login. All other combinations I've tried either show "graylog is restarting" or the original error I posted.
Thanks On Thursday, April 28, 2016 at 4:04:00 AM UTC-4, Jochen Schalanda wrote: > > Hi, > > Try setting the public IP address of your EC2 instance in rest_listen_uri > and web_listen_uri. > > See > http://docs.graylog.org/en/2.0/pages/installation/graylog_ctl.html#advanced-settings > > and > https://github.com/Graylog2/omnibus-graylog2/blob/2.0/files/graylog-cookbooks/graylog/attributes/default.rb#L62-L63 > > for information how to configure this. > > Also make sure that both, the web interface and the Graylog REST API, are > using HTTPS if you want to set this up. Otherwise your browser will most > likely issue a mixed content warning and deny loading data from the Graylog > REST API. > > > Cheers, > Jochen > > On Wednesday, 27 April 2016 22:57:31 UTC+2, Obie wrote: >> >> It looks like the issue has nothing to do with my second interface. >> Instead, I see the issue when I enforce ssl. >> >> On Wednesday, April 27, 2016 at 2:50:56 PM UTC-4, Obie wrote: >>> >>> Fwiw, I didn't move the service--the NFS mount point is the same as the >>> original directory with the original contents moved into it. I stopped all >>> services before making the swap. >>> >>> /var/opt/graylog/data >>> >>> >>> There is no web.conf on the system, but there is >>> /opt/graylog/conf/graylog.conf. This file contains the following >>> http-related variables by default: >>> >>> # REST API listen URI. Must be reachable by other graylog-server nodes >>> if you run a cluster. >>> rest_listen_uri = http://0.0.0.0:12900/ >>> >>> # Web interface listen URI >>> web_listen_uri = http://0.0.0.0:9000/ >>> >>> # REST API transport address. Defaults to the value of rest_listen_uri. >>> Exception: If rest_listen_uri >>> # is set to a wildcard IP address (0.0.0.0) the first non-loopback IPv4 >>> system address is used. >>> # If set, his will be promoted in the cluster discovery APIs, so other >>> nodes may try to connect on >>> # this address and it is used to generate URLs addressing entities in >>> the REST API. (see rest_listen_uri) >>> # You will need to define this, if your Graylog server is running behind >>> a HTTP proxy that is rewriting >>> # the scheme, host name or URI. >>> #rest_transport_uri = http://192.168.1.1:12900/ >>> >>> Thanks >>> >>> >>> On Wednesday, April 27, 2016 at 2:40:03 PM UTC-4, Joi Owen wrote: >>>> >>>> Did you remember to make the same adjustments to the graylogweb config >>>> file? The web service that's sending you the error has its own >>>> configuration that needs to know where it should find the graylog service. >>>> >>>> It's a bit confusing because you have to provide nearly the same >>>> information to server.conf to tell graylog what ports to listen on and how >>>> to refer to itself in uris it provides. >>>> >>>> On our host the web service is configured in >>>> /etc/graylog/web/web.conf. We haven't upgraded to the lastest release so >>>> my info may be stale. >>>> >>>> >>>> On Wed, Apr 27, 2016 at 12:37 PM, Obie <[email protected]> wrote: >>>> >>>>> I installed the v2 GA OVA and have the same issue. >>>>> >>>>> Thanks >>>>> >>>>> On Wednesday, April 27, 2016 at 11:58:22 AM UTC-4, Obie wrote: >>>>>> >>>>>> lol, I see v2 just went GA! MY issue is with the beta version. I'll >>>>>> likely punt and start up the GA release. >>>>>> >>>>>> On Wednesday, April 27, 2016 at 11:57:05 AM UTC-4, Obie wrote: >>>>>>> >>>>>>> I set up the v2 OVA appliance and added an interface (eth1) for >>>>>>> mounting an NFS export for the data directory. That is working fine, >>>>>>> services start, etc., but when I go to the web page I get: >>>>>>> >>>>>>> Server currently unavailable >>>>>>> >>>>>>> We are experiencing problems connecting to the Graylog server >>>>>>> running on *http://<eth1 second interface IP here>:12900/*. Please >>>>>>> verify that the server is healthy and working correctly. >>>>>>> I've set eth0's IP (the primary, web interface) in the following two >>>>>>> lines in graylog.conf: >>>>>>> >>>>>>> rest_listen_uri = http://<eth1 IP here>:12900/ >>>>>>> web_listen_uri = http://<eth1 IP here>:9000/ >>>>>>> >>>>>>> I've tried restarting services and that doesn't do it. Issuing sudo >>>>>>> graylog-ctl reconfigure reverts the above settings to >>>>>>> http://0.0.0.0... >>>>>>> >>>>>>> How do I set the web IP? >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>> -- >>>>> 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/9491d68c-368d-434b-b327-a20a9a5e068c%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/graylog2/9491d68c-368d-434b-b327-a20a9a5e068c%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> No matter what we think of Linux versus FreeBSD, etc., the one thing I >>>> really like about Linux is that it has Microsoft worried. Anything >>>> that kicks a monopoly in the pants has got to be good for something. >>>> - Chris Johnson >>>> >>>> -- 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/ea7173da-2df3-4e7e-a18d-8b3f1dc96ade%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
