Hi Andrew, please use the working Apache httpd configuration from http://docs.graylog.org/en/2.1/pages/configuration/web_interface.html#apache-httpd-2-x and adapt it to your setup.
FWIW, with your current settings, the Graylog REST API would be available at *http://logserver/api/api/* due to your (mis-) configuration. Cheers, Jochen On Friday, 4 November 2016 13:34:02 UTC+1, Andrew Morgan wrote: > > > Thank you for your help thus far, I am now able to get the login screen.My > issue now is that when I try to login, I get the following, I been > searching the net and cant find a solution, any help please? > Error - the server returned: 404 - cannot POST > http://logserver/api/system/sessions (404) > > when I curl I get the following > > curl -XPOST -v http://logserver/api/system/sessions ^C > [root@logserver ec2-user]# ^C > [root@logserver ec2-user]# curl -XPOST -v > http://logserver/api/system/sessions > * About to connect() to logserver port 80 (#0) > * Trying 54.69.228.193... > * Connected to logserver. (54.69.228.10) port 80 (#0) > <-----------------------------this address is the proxy server > > POST /api/system/sessions HTTP/1.1 > > User-Agent: curl/7.29.0 > > Host: logserver. > > Accept: */* > > > < HTTP/1.1 404 Not Found > < Date: Fri, 04 Nov 2016 11:33:02 GMT > < Server: Apache/2.4.7 (Ubuntu) > < X-Graylog-Node-ID: 30cfccc1-68ac-44b4-a064-64b0f0851faf > < Vary: Accept-Encoding > < Content-Type: application/json > < Content-Length: 50 > < > * Connection #0 to host logserver. left intact > > So I believe it is not being proxied over , so this is my apache proxy > configuration: > > <VirtualHost *:80> > ServerName logserver > ProxyRequests Off > <Proxy *> > Order deny,allow > Allow from all > </Proxy> > <Location /api/> > #ProxyPass http://10.1.80.18:12900/ > ProxyPass http://10.1.80.18:12900/ > ProxyPassReverse http://10.1.80.18:12900/ > </Location> > <Location /> > RequestHeader set X-Graylog-Server-URL "http://logserver/api/"; > ProxyPass http://10.1.80.18:9000/ > ProxyPassReverse http://10.1.80.18:9000/ > </Location> > </VirtualHost> > > > > > My graylog config : > > rest_listen_uri = http://10.1.80.18:12900/api/ > rest_transport_uri = http://logserver/ > web_listen_uri = http://10.1.80.18:9000/ > #web_endpoint_uri =http://logserver/ > > > > On Friday, November 4, 2016 at 3:55:19 AM UTC-4, Jochen Schalanda wrote: >> >> Hi Andrew, >> >> the ports are still wrong. You told Graylog to bind the Graylog REST API >> to http://10.1.80.18:9000/api/ but override it with >> http://10.1.80.18:12900/. >> >> Does that look correct to you? >> >> There is, by the way, extensive documentation about configuring the >> Graylog web interface: >> http://docs.graylog.org/en/2.1/pages/configuration/web_interface.html >> >> >> Cheers, >> Jochen >> >> On Thursday, 3 November 2016 18:58:27 UTC+1, Andrew Morgan wrote: >>> >>> I had set it because I am behind a http proxy, is it used for the proxy >>> to communicate with graylog box? I set it to the internal ip address which >>> the proxy will use to get to it >>> >>> >>> rest_listen_uri = http://10.1.80.18:9000/api/ >>> >>> rest_transport_uri = http://10.1.80.18:12900/ >>> web_listen_uri = http://10.1.80.18:9000/ >>> >>> >>> there is nothing in the logs that says error: >>> 2016-11-03T17:54:56.860Z INFO [discovery] [graylog-30cfccc1-68ac-44b4- >>> a064-64b0f0851faf] graylog2/FimGuUaNSuixYjIxtE4heg >>> 2016-11-03T17:54:57.055Z INFO [JerseyService] Enabling CORS for HTTP >>> endpoint >>> 2016-11-03T17:54:59.863Z WARN [discovery] [graylog-30cfccc1-68ac-44b4- >>> a064-64b0f0851faf] waited for 3s and no initial state was set by the >>> discovery >>> 2016-11-03T17:54:59.864Z INFO [node] [graylog-30cfccc1-68ac-44b4-a064- >>> 64b0f0851faf] started >>> 2016-11-03T17:54:59.933Z INFO [service] [graylog-30cfccc1-68ac-44b4- >>> a064-64b0f0851faf] detected_master {X-Cutioner}{hzQkdEGvQV2ktep8euZnAQ}{ >>> 127.0.0.1}{127.0.0.1:9300}, added {{X-Cutioner}{hzQkdEGvQV2ktep8euZnAQ}{ >>> 127.0.0.1}{127.0.0.1:9300},}, reason: zen-disco-receive(from master [{X- >>> Cutioner}{hzQkdEGvQV2ktep8euZnAQ}{127.0.0.1}{127.0.0.1:9300}]) >>> 2016-11-03T17:55:05.869Z INFO [NetworkListener] Started listener bound >>> to [10.1.80.18:9000] >>> 2016-11-03T17:55:05.871Z INFO [HttpServer] [HttpServer] Started. >>> 2016-11-03T17:55:05.871Z INFO [JerseyService] Started REST API at <http >>> ://10.1.80.18:9000/api/> >>> 2016-11-03T17:55:05.871Z INFO [JerseyService] Started Web Interface at >>> <http://10.1.80.18:9000/> >>> 2016-11-03T17:55:05.872Z INFO [ServiceManagerListener] Services are >>> healthy >>> 2016-11-03T17:55:05.873Z INFO [ServerBootstrap] Services started, >>> startup times in ms: {KafkaJournal [RUNNING]=13, OutputSetupService [ >>> RUNNING]=16, BufferSynchronizerService [RUNNING]=29, JournalReader [ >>> RUNNING]=63, InputSetupService [RUNNING]=105, PeriodicalsService [ >>> RUNNING]=147, IndexerSetupService [RUNNING]=3301, JerseyService [RUNNING >>> ]=9227} >>> 2016-11-03T17:55:05.873Z INFO [InputSetupService] Triggering launching >>> persisted inputs, node transitioned from Uninitialized [LB:DEAD] to >>> Running [LB:ALIVE] >>> 2016-11-03T17:55:05.877Z INFO [ServerBootstrap] Graylog server up and >>> running. >>> >>> >>> >>> but still cant log in >>> >>> >>> >>> >>> We are experiencing problems connecting to the Graylog server running >>> on http://10.1.80.18:12900/. Please verify that the server is healthy >>> and working correctly. >>> >>> You will be automatically redirected to the previous page once we can >>> connect to the server. >>> >> -- 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/5ac005ca-7c49-411b-a563-a97d2399c67a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
