Hi Himanshu, Yes, you will need to configure the iptables software firewall to allow traffic on the appropriate service ports. Something like the following will add the accept rule for HTTP traffic over port 80:
iptables -A INPUT -p tcp --dport 80 -j ACCEPT Be sure to save the firewall rules after applying changes so that they persist after reboot. This is assumed to be part of your initial firewall security configuration. Typically you will not want to leave the server operating without iptables enabled due to potential security concerns. Be sure to repeat this process for port 443 if you will be using HTTPS. Many thanks, Wm. Marc O'Brien Scalr Technical Support On Thursday, September 15, 2016 at 6:33:55 AM UTC-6, himanshu jain wrote: > > I think I found the issue, > > While I was rerunning the chef recipes I could see service iptables to be > enabled which acts as firewall in the linux server. I stopped it and I was > able to access the UI. > > Recipe: iptables-ng::manage > * ruby_block[restart_iptables] action create > Recipe: <Dynamically Defined Resource> > * service[iptables] action enable > - enable service service[iptables] > * service[iptables] action restart > - restart service service[iptables] > * service[ip6tables] action enable > - enable service service[ip6tables] > * service[ip6tables] action restart > - restart service service[ip6tables] > - execute the ruby block restart_iptables > > Running handlers: > Running handlers complete > Chef Client finished, 57/103 resources updated in 348.309935093 seconds > > Thanks & Regards, > Himanshu Jain > > > On Wednesday, September 14, 2016 at 4:21:43 PM UTC+5:30, 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.
