-
Notifications
You must be signed in to change notification settings - Fork 453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to access Camera/Microphone, Talk isn't seeing HTTPS #3150
Comments
Seems to be the same problem as with #930 So we show this when the browser responds with: spreed/src/utils/webrtc/webrtc.js Lines 795 to 798 in 204956c
So it seems to be a problem with your server setup ( I think we could split the error messages, but I guess there is not a lot we can do about it. |
Seems to be a client issue... Working properly in Chrome, but still have the https error on Firefox despite having active https certs. |
I got the "move your setup to https" error on Safari/Firefox on iOS. We should warn on unsupported platforms (like iOS without Talk-App and MacOS) as suggested in #154 This issue is probably related to #930 I first thought that my coturn server might be misconfigured, but it also happens inside my local network. (accessing the frontend through https of course). |
It is actually working. Which version are you using? |
NC 18.0.3, Talk 8.0.7, Current iOS/Safari on iPad. |
So Safari 13.1? |
I will check the version tomorrow, but probably 13.1. Same for the Mac and iPhone from someone I wanted to chat with. Do you think coturn could be a problem here? |
When it works with something else on the same device it's unlikely |
I think I found a solution for this: I disallowed camera and microphone access for Safari („Never“). |
Getting the same message “Access to microphone & camera is only possible with HTTPS: Please move your setup to HTTPS“ checking the SSL certificate in the desktop browser gives all green fully ssl supported, and on ios everything works well on safari, but anything other then ios/safari on the mobile gives the message above. I have Nextcloud docker with nginx terminating reverse proxy, so maybe it’s my configuration, but not clear on what the real issue given this message with https clearly enabled on the front end. Any thoughts? |
Please see the comment above: |
@Alphakilo Thank you for your response. I apologize I should have been more clear, I don't have any problems whatsoever using Nextcloud Talk on the ios device while using the Safari Browser, No error messages or anything like that, the video and mic connects as expected when given permission. The problem that I am having is that on that same ios device using either the Chrome or Firefox Browsers I get the error message described above and I am not able to connect the video or the mic to join the call. If it is simply that it is not supported that is not clear from the above error message. The fact that it works on all desktop browsers with no issues and even the iphone's own safari browser, but not the other ones seems strange. @nickvergessen is it correct to assume that on ios, firefox and chrome are not supported when we get the message " Access to microphone & camera is only possible with HTTPS: Please move your setup to HTTPS" and that it is not actually an issue with my setup? |
Looks like I found my answer: stackoverflow.com. And with opening talky in both ios chrome and firefox mic and video are greyed out and can not be enabled, while webrtc is possible it seems only through apple's own ios safari browser. |
In my case it was featurePolicy headers in my traefik config. There are several "security" header articles out there that have camera & microphone disabled. |
Steps to reproduce
Expected behaviour
Camera and audio should be accessible over https
Actual behaviour
Error: Access to microphone & camera is only possible with HTTPS: Please move your setup to HTTPS
Server configuration detail
Operating system: Linux 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64
Webserver: Apache/2.4.38 (Debian) (apache2handler)
Database: pgsql PostgreSQL 12.1 (Debian 12.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
PHP version:
7.3.16
Modules loaded: Core, date, libxml, openssl, pcre, sqlite3, zlib, ctype, curl, dom, fileinfo, filter, ftp, hash, iconv, json, mbstring, SPL, PDO, session, posix, Reflection, standard, SimpleXML, pdo_sqlite, Phar, tokenizer, xml, xmlreader, xmlwriter, mysqlnd, apache2handler, apcu, exif, gd, gmp, imagick, intl, ldap, memcached, pcntl, pdo_mysql, pdo_pgsql, redis, sodium, zip, Zend OPcache
Nextcloud version: 18.0.2 - 18.0.2.2
Updated from an older Nextcloud/ownCloud or fresh install:
Where did you install Nextcloud from: Docker
Signing status
Array
(
)
List of activated apps
Configuration (config/config.php)
Are you using external storage, if yes which one: local/smb/sftp/...
Are you using encryption: false
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Client configuration
Browser: Mozilla/5.0 (Windows NT 10.0; rv:68.0) Gecko/20100101 Firefox/68.0, Firefox Preview
Operating system: OS X, Android
Logs
Web server error log
Unsure how to collect this, the "error.log" file is not accessible for some reasonNextcloud log
I believe this is the relevant excerpt... Didn't see anything else of interest in the log.Browser log
Firefox console (excerpt)
Firefox debugger
Chrome's JS console
Additional Notes
Being that I am using Traefik with LetsEncrypt to generate SSL certs, I've changed my config.php to add:
and
I am accessing the server from an https:// address that is continuing to show A+ security through Nextcloud's security check service.
The text was updated successfully, but these errors were encountered: