Slimstat ignores all the https traffic right?

SlimStat is HTTPS-aware. Could you make sure your Permalinks settings use HTTPS?

Permalinks are definitelly https aware they look like this (in example)

https://domain.bla/wordpress/2013/09/10/sample-post/

What else could I check?

Cheers.

Andrzej

Go to Settings > General and see what you have there.

WordPress Address (URL) https://domain.bla/wordpress

Site Address (URL) https://domain.bla/wordpress

I am not running https on a standard 443 port. Would this affect it?

Cheers.

Andrzej

I will just add that in all cases when I wrote the address domain.bla I mean domain.bla:port – just adding it there.

Cheers.

Andrzej

Take a look at the source code of your pages and see if the admin URL listed in the SlimStatParams JavaScript object is consistent with your permalinks.

It says:

var SlimStatParams = {“ajaxurl”:”https:\/\/domain.bla:port\/wordpress\/wp-admin\/admin-ajax.php”

I think its correct.

I now remember that after I switched to https only I had some entries showing up in SlimStat. The problem occurred gradually later after one of the upgrades I think.

I just checked and I see entries of other users in June 2013 – month after I switched to https only.

What else could I check?

Cheers.

Andrzej

Could you post the URL so that I can run some tests on my end?

Yeah no problem. I didn’t wanted to attract attention to the site by plugging it in here aka. spamming.

https://andrzejl.no-ip.org:30303

Please be aware that:

a) browser TLS 1.2 capable is needed
b) ssl cert is self signed – expect a self signed ssl cert warning

Cheers.

Andrzej

What browser would you recommend? I tried Chrome and Firefox, and I keep getting the following error message:

An error occurred during a connection to andrzejl.no-ip.org:30303.

Cannot communicate securely with peer: no common encryption algorithm(s).

(Error code: ssl_error_no_cypher_overlap)

I use Firefox 23 with a tiny modification.

https://kb.mozillazine.org/Security.tls.version.*

paste this:

about:config?filter=security.tls.version.max

in firefox address bar and change the value of:

security.tls.version.max

variable to 3. This will cause Firefox to ask about TLS 1.2 first. I hear it _MAY_ cause some compatibility issues with older http servers but I have yet to see that to happen. Reverting as You probably guessed is very easy…

Opera under Linux does not work with TLS 1.2.

Chromium under Linux works with tls 1.2 out of the box under ArchLinux. I am surprised that the latest chrome doesn’t work. W3M Linux terminal browser, Konqueror in KDE 4.11.1 are working fine too.

Kind regards.

Andrzej

it didn’t work for me on firefox 23 on mac.

Not sure why would someone mark this topic as resolved… it’s clearly far from it. Marking unresolved posts as resolved MAY increase the solved topic statistics and will look good on a paper but in the end it just confuses users that expect to find solution in a thread.

Camu – there was an upgrade of Firefox to version 24 can You access the website now or is Firefox still struggling to patch the tls 1.2 bug?

Cheers.

Andrzej

Fine, leave it not resolved ?? The issue is clearly your unique setup, not WP SlimStat.

How comes? I am wondering if the tls 1.2 could be the cause… What can I do to try to mend it? Remove plugin and the database entries? It’s just weird. It worked and then it stopped. Maybe after one of the Slimstat upgrades, maybe after one of the ArchLinux upgrades, maybe after wordpress upgrade… Any troubleshooting steps?

Cheers.

Andrzej