.install.sh not creating server config in ./GISportal/config/site-settings/<server name> about gisportal HOT 4 CLOSED

On Wed, Jul 19, 2017 at 7:29 PM, Ben Calton ***@***.***> wrote: Hi Ian, All looks like it should work. The warnings can safely be ignored (we really should remove the chunks of code they refer to). The fact that there is no server config should not necessarily be a problem either; config/global-config-server.js contains the minimum required to get the application running. As you selected no to the SSL and authentication questions in the install script I would expect the 'List of domains with Google authentication settings:' to be empty. I would expect the install script to create a folder using the domain name that you supplied, however, the application will make new directories on-the-fly when the application is accessed via a new domain name. The fact that you are seeing this: GISportal server listening on port 6789 Connected to redis. Redis client ready. tells me that the application is running and should be accessible. There are a couple of potential causes of why you cannot access it, but first I'd like to make sure that it's behaving properly. Make sure the application is running (node app.js), then please run this curl command in a new tab *on the VM* to make a request: curl -o /tmp/index.html http://localhost:6789 If the file that has downloaded (/tmp/index.html) is very similar to the source file in src/index.html then this shows that the app is running properly, but you cannot get to it from your machine. If it's not please post the contents here so that I can understand what's going on. Incidentally, there should also now be a new folder in config/site-settings/localhost:6789 If the index files are similar the application is working. In which case, things to look at: - Firewall enabled on the VM; if this is on please try switching it off briefly to eliminate this - SELinux is enabled? run getenforce to get the status of SELinux currently and if you get an answer of 'Enforcing' try turning this off temporarily too Please let me know if any of this helps Regards, Ben — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#49 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVvwJPf62yMPmTZnb7GGVvh4Bv2k9p2Eks5sPcxmgaJpZM4OcHIW> .

On Thu, Jul 20, 2017 at 11:43 AM, Ian Marang ***@***.***> wrote: Hi Ben, Thank you for your prompt response! OK, I've run the curl command you gave. The '/tmp/index.html' and '/src/index.html' are identical. I checked SELinux and it shows 'Permissive' as the status. I've gone back to my university's server team to confirm on the status of the firewall, but I had another question int he meantime. What exactly is the domain name I should be entering in the browser to access the portal? I just want to confirm that this should be exactly what has been specified in the ./install.sh run. Cheers Ian On Wed, Jul 19, 2017 at 7:29 PM, Ben Calton ***@***.***> wrote: > Hi Ian, > > All looks like it should work. The warnings can safely be ignored (we > really should remove the chunks of code they refer to). The fact that there > is no server config should not necessarily be a problem either; > config/global-config-server.js contains the minimum required to get the > application running. As you selected no to the SSL and authentication > questions in the install script I would expect the 'List of domains with > Google authentication settings:' to be empty. > > I would expect the install script to create a folder using the domain > name that you supplied, however, the application will make new directories > on-the-fly when the application is accessed via a new domain name. > > The fact that you are seeing this: > > GISportal server listening on port 6789 > Connected to redis. > Redis client ready. > > tells me that the application is running and should be accessible. There > are a couple of potential causes of why you cannot access it, but first I'd > like to make sure that it's behaving properly. > > Make sure the application is running (node app.js), then please run this > curl command in a new tab *on the VM* to make a request: > > curl -o /tmp/index.html http://localhost:6789 > > If the file that has downloaded (/tmp/index.html) is very similar to the > source file in src/index.html then this shows that the app is running > properly, but you cannot get to it from your machine. If it's not please > post the contents here so that I can understand what's going on. > Incidentally, there should also now be a new folder in > config/site-settings/localhost:6789 > > If the index files are similar the application is working. In which case, > things to look at: > > - Firewall enabled on the VM; if this is on please try switching it > off briefly to eliminate this > - SELinux is enabled? run getenforce to get the status of SELinux > currently and if you get an answer of 'Enforcing' try turning this off > temporarily too > > Please let me know if any of this helps > > Regards, > Ben > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#49 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AVvwJPf62yMPmTZnb7GGVvh4Bv2k9p2Eks5sPcxmgaJpZM4OcHIW> > . >