I'm trying with Chrome version 56.0.2924.87 and Internet Explorer 11.
Ok, I have to look into this on our test VM - maybe it's a general problem... takes some time
...looks like I can try Alfresco 5.2 AOS on windows 7 with office 2010 this Friday.
That would be appreciated. My installation on fresh server 2012R2 faced the same problem. Blank page and nothing show up.
I tried Alfresco Enterprise Edition (trial) with MS Office 2013 and this configuration faced the same problem. By using webdav everything works fine (both Community and Enterprise). I suppose this is a problem with Share that doesn't set up UNC path correctly. Is something like "file not found". Tomorrow I'll try with MS 2016 version.
You can see the created Url when activating "Developer Tools" in Chrome or Firefox and watch for your document in the Network-Tab.
The provided Url should be something like "ms-wordfe%7Cu%7Chttp://yourIpAddressOrServerName:8080/alfresco/aos/pathtoyourDocx"
when you work without SSL and on the standard port.
SOLVED!
I had mistakenly defined the registry Key
“HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Internet\BasicAuthLevel”
as QWORD (64-bit) and not DWORD (32-bit).
This is a good reference:
Setting up Alfresco Office Services using a non-SSL connection | Alfresco Documentation
That's easy to get the reg-keys wrong. Very good that you found it. maybe min zaw oo has the same issue...
Thanks you Martin! there are two steps inside registery, one to modify and other one to create.
It would be very please if you can send me the guideline to enable SSL, easy way!. Official documentation is quite complicated. Anyway Thanks.
I prefer to set-up a http server (apache or nginx) as reverse proxy in front of alfresco. This also has the benefit to be able to show up a friendly maintenance page when alfresco is down - and you can easily deploy Angular(js) single-page apps for Alfresco directly on the http server or call your also proxied nodeJs app from the same site-name, preventing you from cross-origin problems.
The http Server is then handling the SSL work and your alfresco tomcat won't have to encrypt and decrypt the traffic.
But if you want tomcat to do the "heavy lifting" Apache Tomcat 7 (7.0.76) - SSL/TLS Configuration HOW-TO on the Apache site shows how to SSL your container - should be ok for alfresco, im not sure about the tomcat version (maybe 7.0.59 when using the installer, but SSL config should be the same).
If you want to use the http-reverse proxy approach, look for a setup on GitHub.com - I think there is an nginx example provided by loftux.
Further questions? Then please describe your setup - mainly server os (I'm using Linux and macOs server side), deploying alfresco on premise or in www and if you already have a ssl certificate or need to know how to create or obtain one...
Maybe we/someone/I should create a community.alfresco.com blog article on "how to SSL enable Alfresco" or there is already one...
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.