Hi guys,
I've been struggling the last 3 days, trying to work this out :
Boss said he needs to change the alfresco url from this.mydomain.com to that.mydomain.com.
I thought I could do that easily. I modified the nginx servername as well as some other strings in alfresco-global.properties and share-config-custom.xml.
I restarted Alfresco... and there it began :
- First thing : my custom login page is back to the default one.
- Second : existing users can't login anymore.
There must be something obvious I'm missing, maybe with the DB ? Could you please help me sort this problem out ? I'd be really grateful.
Thanks for your time and suggestions
Best,
Yann
I think changing the serverName and updating the alfresco-global.properties is enough. share-config-custom.xml file change is required in case your alfresco and share are running on different hosts. There is nothing to do with DB in this case.
I am not sure what is your current setup. But considering that you have a proxy host, a db host and a host where alfresco and share is deployed.
I would change:
server {
...
..
server_name that.mydomain.com;
...
....
}
Required so that proper URLs are prepared:
alfresco.host=that.mydomain.com
alfresco.port=80 #As per your current setup. This is an example
share.host=that.mydomain.com
share.port=80 #As per your current setup. This is an example
If you are using CMIS to connect, you may also have to set some of the opencmis properties:
opencmis.context.override=false
opencmis.context.value=
opencmis.servletpath.override=false
opencmis.servletpath.value=
opencmis.server.override=true
opencmis.server.value=http://that.mydomain.com
[Edit]: If share to alfresco communication is configured to via proxy, then share-custom-config.xml is also required to be modified.
<endpoint-url>http://that.mydomain.com/alfresco/s</endpoint-url>
Thank you for your reply and your time.
I think my settings were already correct. Actually, being stuck for too long the day I posted my request, I ended up reinstalling Alfresco Share. I then copied back all config files from the non working Alfresco instance and that did the trick.
Kind regards,
Yann
Hi @ylezy ,
Thanks for reporting how you fixed your issue - this is helpful for other users encountering a similar problem.
Glad you got it fixed.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.