Upgraded to 5.4 and now I cannot connect to C5 Community

Permalink 2 users found helpful
When I try to connect to the community so I can browse for new themes I get this error:

An unexpected error occurred.

A database error occurred while processing this request.

Where should I be looking for more information (which error log) or can someone point me in the right direction on how to fix it?

nathantgross
 
frz replied on at Permalink Reply
frz
hmm. have you cleared your site cache?

is everything else on your site working right?

where did you see this error, and can you provide a screenshot?

best
nathantgross replied on at Permalink Reply 2 Attachments
nathantgross
I cleared the cache folder and everything else seems works fine. I had to tweak the theme after the upgrade but other than that and this community connection problem everything seems to be working.
I also checked my error logs and there is nothing regarding this problem.

Thank you for the assistance.
mlarimore replied on at Permalink Reply
mlarimore
I'm having the exact same problem. All is working fine, but I get :
An unexpected error occurred.

A database error occurred while processing this request.

After clicking on the "Connect to Community" button.

Nice screenshots nathangross!
nathantgross replied on at Permalink Reply 1 Attachment
nathantgross
I upgraded to Version: 5.4.0.5 and I can get to the login to community page but when I login it says: Your site token must be 64 characters.

Screenshot is attached.

How do I set the site token?
mlarimore replied on at Permalink Reply
mlarimore
I second nathangross, again! Same problem. :)
"Your site token must be 64 characters."
andrew replied on at Permalink Reply
andrew
What browser are you folks using?
Mnkras replied on at Permalink Reply
Mnkras
That problem should now be resolved, andrew that was the thing i told franz about
nathantgross replied on at Permalink Reply
nathantgross
The problem should be resolved in the next release or it should be resolved without updating? I'm still getting the "site token" error and I'm on verion 5.4.0.5.
andrew replied on at Permalink Reply
andrew
No. This is not something we've seen before or been able to reliably replicate, so it's not something we've "fixed."

If any of you try and connect your site to the community, and you get the black page which gives you the error, can you view the url of that iframe? When I do so from a test site I've made I get something like this:

http://www.concrete5.org/marketplace/connect?ts=1272901707&csiU...

The csToken has to be there. For some reason it sounds like it's not. Do you have any overrides in any local elements or helpers directories? Can you replicate this behavior if you create a trial site athttp://www.concrete5.org/about/trial/... ?
nathantgross replied on at Permalink Reply
nathantgross
I created a test account:http://testnathan.c5host.com and was able to connect that to the community with my nathantgross account, no errors.

Forgive my ignorance, what do you mean by "overrides in any local elements"?
nathantgross replied on at Permalink Reply
nathantgross
I've used Chrome, Firefox, IE (bleh), and Opera. Same result.
bebop1065 replied on at Permalink Reply
I also keep getting "Your site token must be 64 characters." when trying to connect to the community.

Firefox Safari and Chrome

Thanks.
nathantgross replied on at Permalink Reply
nathantgross
My installation of C5 started with version 5.3 and has been upgraded when there was a new version available.

What versions did you all start on?
bebop1065 replied on at Permalink Reply
5.3 and then upgraded to 5.4. Neither worked for me.

Could this be a curl issue?
nathantgross replied on at Permalink Reply
nathantgross
I created a fresh test concrete install on my hosting account and ran into the same error message when connecting to the community. In my original installation I replaced all the files that mentioned "csToken" from a fresh install and its still not working.
nathantgross replied on at Permalink Reply
nathantgross
How or where is the site token generated?
Casteleiro replied on at Permalink Reply
Casteleiro
I get the same Token 64 error =(
I installed Concrete5 in my server using Simplescripts from my Cpanel

Any solutions?
Thanks,

AC
andrew replied on at Permalink Reply
andrew
Make sure curl or allow_url_fopen is enabled on your server. It sounds like it is not - you should check with your hosting company.
Casteleiro replied on at Permalink Reply
Casteleiro
Alex: [4:57:22 AM] Hello, I just wanted to know if both curl and allow_url_fopen are enabled
Luke: [4:58:52 AM] They are enabled.
Alex: [4:59:03 AM] ok thnks
[4:59:13 AM] have a greaT day

What else can be the problem??
Thanks
andrew replied on at Permalink Reply 1 Attachment
andrew
Hmm. I'm not sure. If you open concrete/libraries/marketplace.php and find the line

$token = $fh->getContents(MARKETPLACE_URL_CONNECT_TOKEN_NEW);

And then print $token after it, do you get anything when trying to connect to the marketplace? There should be a long string of characters on your

http://yoursite.com/index.php/dashboard/settings/marketplace/...

page, above the iframe.

If not, open concrete/helpers/file.php and find the FileHelper::getContents() and start debugging from there. Maybe remove the @ symbol from the file_get_contents() function?
bebop1065 replied on at Permalink Reply
I tried the 'print $token' and I saw no characters. I was unable to locate 'FileHelper::getContents()' within file.php.

Thanks for trying.
andrew replied on at Permalink Reply
andrew
It's actually just named "getContents()" and should be found within concrete/helpers/file.php
bebop1065 replied on at Permalink Reply
CURL is enabled on my server as well, but I still cannot connect to the community.

Is there a workaround?

Thanks.
nathantgross replied on at Permalink Reply
nathantgross
So I ran a traceroute from my server, here are the results:

-------------------------------------------
traceroute to concrete5.org (67.227.135.145), 30 hops max, 40 byte packets
1 69.89.16.1 0.392 ms
2 4.53.40.73 1.735 ms
3 4.69.148.6 27.161 ms
4 4.69.144.134 15.256 ms
5 4.68.110.66 20.835 ms
6 64.209.88.186 55.922 ms
7 *
8 *
9 *
-------------------------------------------

It looks like there could be a problem with Concrete5's ISP. I host with Bluehost.com and I did a traceroute from another Bluehost server and was able to connect to concrete5.org. My server IP is 74.220.219.149

Here's the other traceroute:

traceroute to 67.227.135.145 (67.227.135.145), 30 hops max, 40 byte packets
1 66.147.240.1 0.344 ms
2 172.16.100.10 0.693 ms
3 4.53.40.73 2.069 ms
4 4.69.148.6 15.342 ms
5 4.69.144.70 15.569 ms
6 4.68.110.66 20.921 ms
7 64.209.88.186 55.976 ms
8 209.59.157.224 61.599 ms
9 209.59.157.234 65.626 ms
10 67.227.135.145 64.032 ms
andrew replied on at Permalink Reply
andrew
I will send this to the server people, but it would probably help if you sent the same message to your bluehost folks. It is highly likely this is a problem on their end, not ours. We do, after all, have thousands of sites that have managed to connect to concrete5.org.
andrew replied on at Permalink Reply
andrew
It turns out that we are indeed blocking that IP - but it is for a reason. Apparently a denial of service attack was detected by our server folks from that particular IP address. Not sure when it's going to be unblocked. This is the price that you pay for shared hosting with a large pool of customers.
admin replied on at Permalink Reply
its now a week later and i am getting that same error on a fresh install after not getting it previously. i sent the problem to bluehost, is anyone still getting this error
bebop1065 replied on at Permalink Reply
I've never been able to connect.
davidlbackes replied on at Permalink Reply
From Bluehost--I was having the same token issue and emailed them after doing some digging.

Dear Customer,
this error is happening because concrete5.org has blocked the shared ip of the server which they seem to do quite a bit. Unfortunately there is not a thing we can do about them blocking our servers. You can ask them if they will unblock 66.147.244.161 which is your shared ip and hopefully they will be nice enough to do so. If not then your best bet would be to get yourself a dedicated ip which is not shared and is not likely to be blocked by them allowing you to connect to the concrete 5 community. You can get a dedicated ip by clicking the dedicated ip tab at the top of cpanel when you log in. Sorry for the trouble on this but that is what the problem is.

Thank you,
Eric
Level II Tech Support /Scripting

Andrew: does this mean that Concrete5 is going to be pretty hit-or-miss on shared hosting companies? I understand your "that's the price you pay for shared hosting..." but C5 is a *free* CMS. I'm assuming that a large part of your customer base is using cheap hosting--doesn't that go hand in hand with a free CMS?
moremoney4u replied on at Permalink Reply
I am getting "Your site token must be 64 characters" error, too, when trying to connect to the community. I just signed up with hostmonster and installed the latest version (stable) of concrete5 through my Cpanel (simplescripts). I tried Firefox and Chrome. Called support and they said the problem is not on their side and advised me to contact concrete 5. Is there a solution for this yet? Are they going to continue blocking my shared hosting company? This sucks. I appreciate any help you can give me.

Firefox Safari and Chrome
funkijamr replied on at Permalink Reply
funkijamr
I'm having the same issue with a new site, though am not with an old one), both hosted on hostmonster. I also got a dedicated IP and still getting the error. CURL is enabled and php.ini settings are as instructed in this (and other) threads.

I had been hoping to purchase some of the blocks from the c5 marketplace, wondering if I should be looking at other CMS or website builders...?
andrew replied on at Permalink Reply
andrew
Could you private message me some FTP/admin access credentials? I'm trying to stomp out these issues.
funkijamr replied on at Permalink Reply
funkijamr
I am still getting the same error, "Your site token must be 64 characters".

I sent UIDs to Andrew in a PM last night, awaiting an update...