As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
I have installed Alfresco Community on AWS EC2 with S3 integration.
I am getting this error message if I am leaving the server idle for few hours and when I try to login as an admin or user.
I need to stop and start the alfresco service to resume the system to work properly.
Please let me know if I can do something to address this issue.
Thanks,
VJ.
Please, share the alfresco's log here in order to get help.
That image is not usefull at all to identify the error.
I have the same problem after a fresh install. Login in to alfresco share gives me the Somtehing's wrong ....
There is not output in alfresco.log.
Installed Version 201704.
Ok, simply running it with IP is working. The problem is how I should configure it to be accessed behind a reverse proxy if the proxy access alfresco on port 80.
With this config I get the Somthing's wrong bla bla:
dir.root=/srv/alfresco/alf_data
alfresco.context=alfrescoalfresco.host=alfresco.example.comalfresco.port=80alfresco.protocol=http
share.context=shareshare.host=alfresco.example.comshare.port=80share.protocol=http
I change the config to
alfresco.context=alfrescoalfresco.host=alfresco.example.comalfresco.port=443alfresco.protocol=https
share.context=shareshare.host=alfresco.example.comshare.port=443share.protocol=https
But after a restart, alfresco is still listening to 8080 and 8443. What am I doing wrong?
You can rely on the following blogpost to achieve what you want
- Change Alfresco ports in Alfresco 5 - zylk
Thank you. Just to clarify: What for are those settings
alfresco.port=443alfresco.protocol=https
share.port=443share.protocol=https
if I still have to change it in server.xml? Probably I have still not understood the concept behind the config files used for alfresco.
got it: URL Generation Parameters (The ${localname} token is replaced by the local server name)
it's up an running now, thanks!