fopen warnings - please ignore

[whole diary]

[grahame]

If you see this message - don't worry

Warning: fopen(./loggy.txt): failed to open stream: No such file or directory in /home/firstgreatwestern/httpdocs/coffeeshop/index.php on line 39

Warning: fgetcsv() expects parameter 1 to be resource, boolean given in /home/firstgreatwestern/httpdocs/coffeeshop/index.php on line 41

Warning: fclose() expects parameter 1 to be resource, boolean given in /home/firstgreatwestern/httpdocs/coffeeshop/index.php on line 51

I know exactly what it is (actually knew it might happen when I put in some recent code to act against a distributed denial of service attack) and it will make no difference to the rest of your page

I am attempting a fix, but it's generated only rarely and when a number of things going on all happen at the same time, and it's "fail safe".  I have no easy way to see if my fix works.

[stuving]

I don't know if this is related, but I'm sure it's got something to do with you ... Bitdefender has complained that

firefox.exe attempted to establish a connection relying on an unmatching security certificate to new.passenger.chat. We blocked the connection to keep your data safe since the used certificate was issued for a different web address than the targeted one.

I've made an exception of it, but just sayin'.

[grahame]

I don't know if this is related, but I'm sure it's got something to do with you ... Bitdefender has complained that

firefox.exe attempted to establish a connection relying on an unmatching security certificate to new.passenger.chat. We blocked the connection to keep your data safe since the used certificate was issued for a different web address than the targeted one.

I've made an exception of it, but just sayin'.

I am in the process of updating http and https for the passenger.chat domains and am in the process of moving them from 88.202.183.177 and 88.202.183.215  (which were insecure) to 213.165.84.74 (where I have a secure option).  Yeah - I suppose there are possibly some warning for the next few hours at least while it settles down.

All https certificates issues should be for 213.165.84.74 ... I am a bit concerned that I may have bungled something up in doing the work - will double check.  But both domains are "ours"

[grahame]

A follow up - if you all up the passenger.chat domain with "https" (not something I have ever invite to you do) you may get something like



or



but please bear in mind I am working on this so it is likely to be updated. Click on the images above to see what they look like now!