Hi Himanshu, All of Jay's noted points are valid and worth testing. Additionally, please ensure that you have followed all of the basic installation guide <https://scalr-wiki.atlassian.net/wiki/display/docs/Installation+and+Upgrade+Instructions> including the steps to manually run the wizard with "sudo /opt/scalr-server/bin/scalr-server-wizard " as well as reconfigure as Jay noted. Once this has been completed, and scalr-server-manage shows all Scalr services as running, you should be able to successfully access the login page for your installation. Let us know if troubles persist.
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Wednesday, September 14, 2016 at 9:16:43 AM UTC-6, Jay Farschman wrote: > > Himanshu, > > You didn't tell us which version of Scalr you are running, or which > operating system you are working on.... but it does seem clear that you > checked the firewall. Here is a little background on my setup. My > /etc/scalr-server.rb is setup to allow access on port 443. This is a > really simple thing to do: > > routing[:endpoint_host] = "10.xxx.xxx.xxx" > routing[:endpoint_scheme] = 'https' > > > If you make a change be sure to run > > scalr-server-ctl reconfigure > > > Second, there is a nice tool "scald-server-manage" that maintains all of > the services (like Monit): > > # scalr-server-manage > crond RUNNING pid 23608, uptime 58 days, > 15:42:35 > httpd RUNNING pid 7446, uptime 58 days, > 1:01:23 > memcached RUNNING pid 23591, uptime 58 days, > 15:42:35 > mysql RUNNING pid 8544, uptime 58 days, > 1:00:45 > rrd RUNNING pid 23040, uptime 58 days, > 15:42:36 > service-analytics_poller RUNNING pid 23017, uptime 58 days, > 15:42:37 > service-analytics_processor RUNNING pid 23553, uptime 58 days, > 15:42:35 > service-dbqueue RUNNING pid 23015, uptime 58 days, > 15:42:37 > service-msgsender RUNNING pid 23032, uptime 58 days, > 15:42:37 > service-plotter RUNNING pid 23065, uptime 58 days, > 15:42:36 > service-poller RUNNING pid 23057, uptime 58 days, > 15:42:36 > service-szrupdater RUNNING pid 32120, uptime 58 days, > 15:12:02 > zmq_service RUNNING pid 23631, uptime 58 days, > 15:42:34 > > > When I run netstat on the Scalr server I see both port 80 and 443 serving > up requests > > # netstat -tupan |grep LISTEN > tcp 0 0 0.0.0.0:80 0.0.0.0:* > LISTEN 3155/httpd > tcp 0 0 0.0.0.0:22 0.0.0.0:* > LISTEN 965/sshd > tcp 0 0 0.0.0.0:443 0.0.0.0:* > LISTEN 3155/httpd > tcp 0 0 127.0.0.1:6270 0.0.0.0:* > LISTEN 3155/httpd > tcp 0 0 127.0.0.1:6271 0.0.0.0:* > LISTEN 3155/httpd > tcp 0 0 127.0.0.1:6272 0.0.0.0:* > LISTEN 23191/python > tcp 0 0 127.0.0.1:6280 0.0.0.0:* > LISTEN 8357/mysqld > tcp 0 0 127.0.0.1:6281 0.0.0.0:* > LISTEN 23591/memcached > > > > I wonder what happens when you try netcat or nc (depends on your OS). Try > this from you Scalr Server: > > # nc -vv localhost 80 > Connection to localhost 80 port [tcp/http] succeeded! > > > or maybe try curl. My Curl command returns a document with the <title>Scalr > CMP</title> > > curl http://localhost > curl -k https://localhost > > > You may want to look at the log files: > > /opt/scalr-server/var/log/httpd > > > Hope this helps. > > > On Wednesday, September 14, 2016 at 4:51:43 AM UTC-6, himanshu jain wrote: >> >> Hi, >> >> I am newbie in Scalr. I installed Scalr in my test lab intending to >> manage all the hypervisors to start with. >> Problem: >> I am unable to access scalr UI/wizard. It shows me unable to connect to >> the site. >> Locally I can see that scalr is listening at port 80. I am able to browse >> the site locally. >> I checked for firewall blockage locally as well as enterprise, There is >> no firewall service running in the server and this seems to be uneachable >> even for the neighbouring servers which are in same subnet and no firewall >> in between them. >> While server is reachable at port 22 it is unreachable at port 80 via >> telnet. >> >> Please suggest. DO let me know if any logs or any more information >> required. >> >> -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
