Hey everyone, I’ve got a odd situation.
I’ve deployed several Nextcloud 12 OVA’s from (https://www.techandme.se/nextcloud-vm/) and none of them are accessible from Internet Explorer… all IE says is “This site can’t be reached” but Chrome, Firefox, and Edge all work fine.
any assistance is greatly appreciated.
Maybe related to missing HTTP 2.0 support on non Windows 10? http://caniuse.com/#search=http%2F2
Also make sure that IE is not running in legacy Intranet mode which happens in local networks
To add some more details.
I’ve tried from Win7 and Win10 machine inside and outside the network with the same results.
A friend setup nextcloud 12 using the vmdk from Techandme, his works fine from any IE…
We’ve ran through every menu in the webadmin and nothing is different.
Hi,
What is a Wireshark trace from the Windows machines with IE saying?
Not a Wireshark master but it looks normal till the machine running IE ends the session.
Frame 243: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: Dell_ec:02:ff (bc:30:5b:ec:02:ff), Dst: HewlettP_fc:8a:1d (a4:5d:36:fc:8a:1d)
Internet Protocol Version 4, Src: 192.168.201.xx, Dst: 184.68.2xx.xxx
Transmission Control Protocol, Src Port: 58922, Dst Port: 443, Seq: 183, Ack: 6432, Len: 0
Source Port: 58922
Destination Port: 443
[Stream index: 7]
[TCP Segment Len: 0]
Sequence number: 183 (relative sequence number)
Acknowledgment number: 6432 (relative ack number)
0101 … = Header Length: 20 bytes (5)
Flags: 0x011 (FIN, ACK)
Window size value: 16185
[Calculated window size: 64740]
[Window size scaling factor: 4]
Checksum: 0x10ee [unverified]
[Checksum Status: Unverified]
Urgent pointer: 0
Hi,
But actually you don’t want the session to be closed 
The packages before that close would be interesting to find out why the connection is not established correctly. I don’t know if it is easy to post the trace here or rather upload it somewhere.
I had the Same issue.
a quick and dirty fix would be:
nano /etc/apache2/sites-enabled/your_nextcloud_fqdn.conf
just comment
# SSLHonorCipherOrder on
Then it shall work on IE 11 (Win7, Win2012r2, etc…)
Use at your own risks: I do not know what are the security issue with that option disabled!!