subdomain mapping results in looping "restarting epesi"

remat457

Hello,
When I try to map a subdomain to my EPESI install (mydomain/epesi) it continuously loops saying "restarting epesi" over and over. Any ideas why?

For example trying to map something like:

"login.mydomain.com"

to point to the install which is:

"mydomain/epesi"

Thanks!

remat457

Just an update but this now works. I think that there was a delay in the host settings.

remat457

I spoke too soon. It is doing it again. Any ideas?

ETA: Found this post: viewtopic.php?f=6&t=239&p=895&hilit=epesi_dir#p895
Is it saying to just delete the values in the two session + history tables?

ajb

Hi,

How you're trying to redirect?

Regards,
Adam

remat457

Hello,
I am using my web hosting's subdomain option which I point to the /epesi folder. Not sure how it works under the hood though. It doesn't appear to be using .htaccess. Any help is appreciated! Thanks

ajb

You could try to set EPESI_DIR in data/config.php

define('EPESI_DIR','/epesi/');

It should be auto detected, but when it's not correct value, then EPESI won't work.

Is this really necessary to use epesi.example.com instead of example.com/epesi/ ? :wink:

Regards,
Adam

remat457

Thanks for the reply. That line is already in my config.php 🙁

It's not a show-stopper for me, but I was hoping it was just something simple.

jasiek

EPESI can run from any virtual directory (example: www.yourdomain.com/crm) or from subdomain (example: crm.yourdomain.com). Most of our installations are run from the subdomain address (epesi.somedomain.com).

My suggestion is to keep your existing installation for now and perform a clean installation of EPESI in your subdomain address with a new database (epesi2 for example). If it works then just copy your mydomain/epesi installation over the subdomain address and edit config.php file to point to the correct database (epesi).

remat457

That is an excellent suggestion, in fact my next question was going to be how can I move my install into a lower level directory -- you have answered it before I even asked!! 🙂

As an update I turned off my host's subdomain redirection and modified the root level .htaccess directly - that worked and EPESI starts up fine. So, it is definitely related to how the host does their redirection.

Thanks for all the help! Great product, BTW.

jasiek

I am glad to hear it worked for you. And thanks for kind words 🙂

remat457

Just in case anyone else has the same problem, I found another workaround. For subdomain redirection, I didn't realize, that my host allows putting a URL in place of the /path. So, in a nutshell with the FQDN (e.g. http://mydomain.com/epesi) works too! Wacky internet.

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge