Hi Samuel, it looks like it is installed correctly. The blank page is happening because you do not have a tenant that is created for the host 87.106.207.149 . So if you go to http://87.106.207.149, it is not functional.
You will first need to log in to the "Admin Tenant" of the server. You configured what the host of the admin tenant should be in the config.js file during the installation procedure [1] with the property "config.server.globalAdminHost". You need to make it so that when you go to that host, the IP that is resolved is 87.106.207.149 -- which would be done with a DNS entry. From there, you will be able to create a new tenant with a new host (e.g., tenant1.example.com), which will also need a DNS entry. I recommend using a wildcard DNS entry such as *.example.com, so that you can map "admin.example.com" to your admin host, and then create any number of tenants without a new mapping, such as "tenant1.example.com", "tenant2.example.com", etc... Hope that helps, Branden [1] https://github.com/oaeproject/Hilary#hilary-configjs On Thu, Jul 18, 2013 at 2:20 AM, Samuel Gutiérrez Jiménez-Peña <samuelgutierrezjime...@gmail.com> wrote: > Hi Branden, > > then this may be the problem, and therefore I can't see it well. > > I've stopped Apache service, before run OAE, to not takes the port80 that > Nginx need, to see if it worked properly, but I still get the blank page. > > I have to make sure before buying another server to OAE, which in this > working properly. Could be why you told me the DNS? The etc/hosts file is > stills the same as last time with: > ---------------------------------------------------- > 87.106.207.149 admin.oae.com > 87.106.207.149 tenant1.oae.com > 87.106.207.149 0.etherpad.oae.com > ---------------------------------------------------- > > Regards, Samuel. > > El 17/07/2013, a las 20:14, Branden Visser <mrvis...@gmail.com> escribió: > > Hi Samuel, > > You have the Apache web server on the same machine. Nginx and Apache are > both web servers, so having both on the same machine is redundant. It's > likely that Nginx didn't start correctly because it will try and use the > same server port as Apache. > > You'll need to do one of the following: > > a) Host OAE on its own machine(s) away from your Apache server. Depending on > how many users you intend to support and what kind of availability you want > to achieve, it might be worth spreading some components to different > machines any way; or > b) Configure Apache to proxy directly to your Hilary app server and > uninstall Nginx. > > Note that OAE is not tested behind Apache, but in theory it should be > possible. It will just require more testing and knowledge of both Apache and > Nginx to translate the configuration. > > Thanks, > Branden > > > > On Wed, Jul 17, 2013 at 1:52 PM, Samuel Gutiérrez Jiménez-Peña > <samuelgutierrezjime...@gmail.com> wrote: >> >> Hi Branden, >> >> I would have to look well the configuration of DNS to do it properly, If >> I have any questions about that I would ask you by mail. >> >> With respect to the server's home page is the index.php created in >> var/www/ when I go to http://87.106.207.149, open that file. Also when I >> start OAE in that configuration server runs in the same direction, getting >> display a blank page instead of index.php OAE. >> >> What files and what settings should be to not to overlap? >> >> Regards, Samuel. >> >> El 17/07/2013, a las 19:36, Branden Visser <mrvis...@gmail.com> escribió: >> >> Hi Samuel, >> >> To deploy for an environment that users can access from their computers, >> there will need to be an entry in a DNS server (either an authoritative DNS >> host such as Dyn.com so all users on the internet can access it, or a DNS >> server hosted within your intranet if you just want users within your >> organization to use it). >> >> When you say there is a conflict, do you mean that there are other >> applications installed on the same machine that are picking up the default >> web ports? What is the "server homepage", is that hosted on the same machine >> you installed OAE on? >> >> Thanks, >> Branden >> >> >> >> On Wed, Jul 17, 2013 at 12:28 PM, Samuel Gutiérrez Jiménez-Peña >> <samuelgutierrezjime...@gmail.com> wrote: >>> >>> Hi Branden, >>> >>> I understand that changing the etc/hosts file on my computer can access >>> the development environment and also to not overlap both directions, also >>> putting 127.0.0.1 (localhost) in etc/hosts. >>> >>> At this point, my intention is to implement a production environment on a >>> server, but I can't understanding very well the steps. The installation was >>> performed correctly with your help, but now I need the configuration to >>> avoid overlaps these addresses. I attach the etc/hosts file from server, >>> where you can see the configuration that I've made: >>> >>> >>> >>> I think that the cause of the overlap is that 87.106.207.149 address is >>> redirected to the server home page, so OAE overlaps this page. I don't know >>> what would be the configuration for any user could enter in OAE without >>> touch the etc/host, to be a production environment. >>> >>> If you needed any more file to understand a little more the server, ask >>> me. >>> >>> Regards, Samuel. >>> >>> El 17/07/2013, a las 16:43, Branden Visser <mrvis...@gmail.com> escribió: >>> >>> Hi Samuel, >>> >>> I think this goes without saying but I want to make sure it's clear, that >>> updating your /etc/hosts file is only sufficient for a local development >>> environment / local trial. If you want to set up the system on a server that >>> other users can use, you'll need to actually make a DNS entry for the >>> server. >>> >>> That said, if you want to set up an /etc/hosts entry on a subdomain of a >>> remote server (that only you can resolve), that is possible without >>> conflicting with a remote server, so long as it is a subdomain. For example: >>> >>> Say you have a remote server set up at www.example.com, which resolves to >>> IP 123.45.67.89. You can set up your local development environment with an >>> /etc/hosts entry like this: >>> >>> 127.0.0.1 oae.example.com admin.example.com >>> >>> And those will not conflict with "example.com", or "www.example.com". >>> >>> >>> >> >> > > _______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
