I installed latest version of Onlyoffice Docs Community Edition using Installing ONLYOFFICE Docs for Windows on a local server - ONLYOFFICE on a Windows Server 2012 Virtual machine. I can see the Welcome Screen on the Document Server Vm, on the Sharepoint Server Vm and also on the user machine.
I also installed Sharepoint Integration v1.2 on a Sharepoint 2016 on premise using ONLYOFFICE Api Documentation - ONLYOFFICE SharePoint integration solution (Sharepoint is running on a Windows Server 2012 R2). I added there the IP address of the Document Server with preceding “http” in the Onlyoffice settings.
If I open my Sharepoint site (using https) and click the button “Open in Onlyoffice” on a .docx document, I can see the error “Sorry, something went wrong” on a new tab. Why?
Can the problem be because of https is not enabled in the Document server or my network structure is using ADFS?
Can the problem be because of https is not enabled in the Document server or my network structure is using ADFS?
That’s right. If your storage (Sharepoint) is using https, then Document server should use https too. Otherwise, you will face mixed content issue. Please try to get SSL certificate for your Document server and reproduce the issue. Please let us know the result.
It seems that you cannot enable https on Onlyoffice Docks if you have it installed on Windows Server with an exe file (at least I cannot find a documentation for that, only for Onlyoffice Groups and Workspace).
It seems that you cannot enable https on Onlyoffice Docks if you have it installed on Windows Server with an exe file (at least I cannot find a documentation for that, only for Onlyoffice Groups and Workspace).
and I can open localhost and oo.dev.local (after editing /etc/hosts) using http:
Please note that docker installation doesn’t imply additional changes to the configs. Everything should work out-of-the-box. Are you using totaly clean OS in your test?
LETS_ENCRYPT_DOMAIN=oo.dev.local
Did you blur your domain name or did you try to get SSL cert for top level domain name (for example, test.my.local). Please note, that LetsEncrypt doesn’t support local domain name.
I installed Onlyoffice Docs on CentOS VM using Docker and enabled HTTPS on it and I also installed Sharepoint Integration v1.2 on a Sharepoint 2016 on premise. I can call up the Document Server page from the Sharepoint VM. I configured the Document Server Adress in the Onlyoffice settings in Sharepoint.
If I use the button “Open in Onlyoffice”, I get the error " Sorry, something went wrong" and the redirection does not take place (I am still on Sharepoint). I investigated in the logs using UlsViewer and found out that the 0x80070005 (Access denied) error occurred when I am using the button.
But in the Sharepoint Administration in Authentication Providers is “Anonymous access” and “Trusted Identity provider” with the ADFS enabled, but not “Require Use Remote Interface permission” and “Enable Windows Authentication” (in contrast to the video tutorial of the installation of the sharepoint connector).
I also checked under Anonymous Access Restrictions “Permissions to None”.
The error looks like a problem with Default zone. Please double check it. ‘Enable anonymous access’ should be ON. The rest of the settings on this page (Authentication Provider) do not need to be touched.
Also, you can make screenshots of your Authentication Provider and Anonymous Access Restrictions pages and share them with us.
Go to Anonymous Access Restrictions and choose Default zone in drop-down menu. Anonymous User policy is left as it is (None - No policy).
If that doesn’t help, please run a test. Go to Authentication Providers Settings and enable checkboxes which you disabled before (Client Object Model, Windows Authentithication, etc.) According to our guide, there’s no necessary to disable it, but I see a disabled one on your first screenshot.
Even if I select default zone and save this configuration. If I then open Anonymous Access Restrictions again, “All zones” is selected again.
I also enabled Client Object Model according to your guide but that doesn’t help though. I cannot disable “Trusted Identity Provider” (because this is the authentication I am using) but even if I enable “Windows Authentication” it still doesn’t work.
Could you please run a test? Create a new user on Windows server > grant the user rights for Farm and Web Application > try to reproduce the issue via the new user account. Will the result be the same?
I also installed the SharePoint Connector on another SharePoint 2016 on premise but I got the same result.
And can it also has something to do with the Authentication settings in the IIS? I remember that if I wanted to login in SP Central Administration, the Windows Authentication failed (despite of I was able to login in the Windows machine with the same credentials). I solved the problem by disabling the Windows Authentication and enabling the Basic Authentication in the IIS. Though I don’t know if that problem has something to do with the current problem because I was able to login in my SP since the beginning (because Anonymous Authentication is already enabled).
I meant that the issue may be related to Windows administrator account. So I suggested a test with creating another user to check it out. Could you please run the test and let us know the result.
