I have freshly installed Centos7 Os on my machine and it has been observed that Optin message(Allow / Disallow) of browserpush came for the https site stops working.
I have checked this with multiple websites but none of them is working which is working on chrome browser.
Anyone having any idea how to rectify this?
You are probably using an Extended Support Release of Firefox and web push is currently disabled on that versions.
Related
I have an Electron app in the Mac AppStore that is essentially just a wrapper around a hosted web app. A few months ago one specific thing has stopped working in this app. I'm using redux-offline to sync changes to the server and this is just not happening any more.
It's working when running it outside of Electron - in any modern browser.
All other requests are working fine.
It's working when debugging it locally.
It's working when running the built version locally.
BUT it fails in the published Mac App Store version. I'm not catching any errors in my logs (server-side or client-side). I just upgraded to the latest Electron (electron#4.1.4, electron-packager#13.1.1) hoping it would solve it - to no avail. I don't even know how to properly debug it since it's only failing in the published version.
Any ideas? On causes, solutions or ways to debug it?
Seems like your application closes by itself. Check all of app.quit executions. For me issue was that app.requestSingleInstanceLock() returns the wrong value for Mac Store build. Please check this issue, if the problem is related to app.requestSingleInstanceLock().
I've tested this on Microsoft Edge and Chrome and its working.
Update: It's working now on Firefox
I have the same issue currently. This is a compatibility issue with Firefox version 64.0. Previous version 63.0.3 works with Google Cloud Shell but version 64.0 released on 2018-12-11 shows Cloud Shell empty.
You can use other browser or fix it temporarily by reverting back to older Firefox version from https://support.mozilla.org/en-US/kb/install-older-version-of-firefox.
There was a problem with Google Cloud Shell terminal emulator, but it has since been fixed.
Environment:
macOS Sierra 10.12.6, Chrome 61.0.3163.100 (Official Build) (64-bit).
Trying to load vSphere web client crashes with "Shockwave Flash has crashed" error.
Tried following but none helped so far.
Removed latest Google Chrome PepperFlash plugin 27.0.0.170 and replaced it with 27.0.0.159 in ~/Library/Application Support/Google/Chrome/PepperFlash.
Enabled running flashes in chrome and added exceptions to the URLs of vSphere
Restarted chrome browser
As a workaround, tried firefox browser to access vSphere web client but even there got the "The adobe flash plugin has crashed" error.
Same vSphere web client works from Mac thats of 2014 but running same environment as above. This is strange that same Mac Version and Chrome version combo works on 2014 mac but not in 2016 mac.
Can someone share any ideas that could solve this?
Thanks a lot.
The instructions from vmware [1] for installing an older version for Firefox worked for me on MacOS 10.12.6 on a 2017 Mac. I did not try to get it working under Chrome.
[1] https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2151945https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2151945
You could reinstall the archived versions of adobe flash to 27.0.0.159.
https://forums.adobe.com/message/9892441#9892441
After that, it will be work. See the above link to figure it out.
I do have the FortiGate client installed and it is not disabled. It worked until I upgraded Firefox to version 22. How do I get this to work with the new version?
This a known bug related to Firefox issue. SSl vpn client plugin's would not work if you are running Firefox version higher then 20 Reference to bug id (0211153).The purposed workaround at this time would be to download stand alone sll vpn client.Please see the link given below for downloading stand alone ssl vpn or go back on a previous version (like 21)
Download SslvpnClient.msi from http://dekiwiki.ties2.net/Fortinet/Fortinet_SSL_VPN_Client_Installers
support guys in the office can't help and everything has been fine for the last couple months until today. Running OSX 10.6.3 and 1 of only 2 users on mac. Can access a staging server when remoting in to a pc near my desk but not able to access via any of the browsers on my mac (Chrome, Firefox or Safari). An example staging server would be http://mesoderm:8080/...
Error is simply: Oops! Google Chrome could not find mesoderm:8080.
I can connect to the internet and remote in to a nearby pc as mentioned above.
Strange why it would all of a sudden do this and it's incredibly annoying! Any ideas would be greatly appreciated.
Regards,
Ryan
Investigate your firewall rules. This is most often the cause of this kind of problems.