Thread

buridan, I’m hesitant to post here because I think people are trying to help you, and what you quote from me was just to tame a possible false lead so the help can keep focused.

Look above, and you’ll find Greg Salt was asking you a very non-generic question; rather it is a precisely targetted one to version assessment, which is where you indicate you are having trouble. Greg is consistently one of the best.

You also received help direct from a very central developer on the javascript issue.

Sue came back to you to be sure if you were ok. Support is not rapid these days, perhaps because as a tweet from the EE oval office shows, support persons are being asked to handle sales loads.

On this version code thing, given that you have the folder and file permissions you show, with a clean installation, another possibility can be that there is a network routing problem to the version server. These do happen; they are often temporary; they often recur. The internet is a bit of a mess in enough locales these days, due to big boys’ games.

If the problem here is that you have a client who’s seeing the error message, I believe you can ameliorate that by turning off New Version Auto Check in your Admin>General Configuration. It’s been done before.

Regards,
Clive

Clive,

I’m aware that Greg, Sue, John, et al are overburdened with support requests, working into the wee hours of the night and on weekends, and doing a great job under these circumstances. Yes, they’ve all been very helpful and patient with me. I’m just frustrated and your post set me off. My apologies.

Best,
buridan

Buridan, thanks, on behalf of everyone, and I do understand well enough.

There’s a kind of interesting riddle afoot in the world, about dealing with imperfect systems, isn’t there.

Here, the important thing has seemed that we work out the ways that work to adapt, and in that way make everyone’s overall situation better.

Take care and regards,
Clive

buridan, our apologies for not being able to assist with this issue immediately. The problem you describe I’ve seen happen once, and right afterwards it didn’t happen again. I suspect it may have been a glitch on our end, which is why I asked if it was still happening. I haven’t seen it occur since that first time you posted.

Turning off the new version check is one way to keep this from happening again, but can you replicate it yourself on any other install? I no longer can. I have sites hosted on EngineHosting, MediaTemple and a generic cPanel install from another company. I open those sites up several times a day and don’t get the error. I still have the New version check turned on.

I did have some weird things happen a few days ago when I was at Panera’s where they have a bit of a firewall. Going back home, the same site was fine.

Can you replicate this anywhere else?

Hi,

I’m not sure if this thread needs help anymore, but if anyone else came across this they might be wondering.  I JUST had this error pop up where EE couldn’t verify the version number, but I was working locally with some interesting firewalls and monitors in place, and I knew the error occurred right after I mis-clicked trying to hastily pass an “Allow/Deny” prompt from my security setup.

Trying to hunt down the resolution I found that I had inadvertently denied a httpd TCP connection to mojomotor.com on TCP port 80. This was what my local install was trying to access to determine versions.  I ended up clearing out my cache for the browser, restarting my machine, and finally, manually deleting the file “current_version” in the “site/expressionengine/cache/ee_version” folder.  This prompted the firewall to check with me again, where I allowed the process, and the problem resolved itself: new “current_version” file created in cache, no more error prompt upon login.  Basically, with the denied connection in place and that situation cached, the problem was recurring. By wiping the slate clean and removing the block, the fresh request and setup worked properly.

This coincides with Sue’s Panera incident, where a firewall or security measure conflicts with an outbound request by EE for information.  That, combined with a cached file that may cause repeated reloads to not reflect any change, might be the root of the problem.  Now, I’m not sure if all the above steps were absolutely necessary (for example, I was hoping the restart would also reset temporary security rules, but that didn’t help), but I thought I would share to help find the root of the problem, and help any other users out there that work locally and were trying to figure out this problem.

I am not sure (the devs would be able to answer for certain), but I think the request for version number (the connect to mojomotor) is done on the client side (meaning your browser accessing the EE Control Panel, not the EE install side itself).  If that’s the case, then the issue with being unable to verify version number would reside on either the connection and security provisions of the user (e.g. browser settings, firewall settings, connection setup, etc), or the script used to make the information request from mojomotor.com.  The latter is less likely though, at least mechanically, because I assume it’s a rather simple function, but you never know.  The culprit definitely seems to more likely be a security issue blocking the request.  As far as the cache handling or other implied issues, well, that’s a whole other thread I think 😊

Hopefully this helps… sorry if it’s long winded and overly technical.  I’m writing more to help the devs pinpoint the problem and give a definitive answer than anything else.

Hi jonny,

Thanks for your note but the check is done serverside and not clientside. I’m not what might have caused this to happen for you but mojomotor.com and expressionengine.com do use the same IP address so denying access to one would cause an issue.

@buridan, where are you with this?

Cheers

Greg