I set it up using localhost:11211 like my host said to do. I then upload the new constants.php and then continue. When I do this, I get this error:

Sorry, there is a problem

Something went wrong. Please try again.

Error code: EX2

Try using 127.0.0.1:11211 instead of localhost

 

Try using 127.0.0.1:11211 instead of localhost

Thanks for the response.

I did. Same issue, unfortunately.

If you dont get any error during configuration change in ACP, I would sugeest clearing cache via System->Support ->Something isn't working correctly.

That was what had helped me when I was trying to install memcached on the server and got the error you mentioned 

This unfortunately did not work, either. I also have a support ticket opened and they stated that there are some issues with 4.0 and memcached that are addressed in 4.1.

 

This unfortunately did not work, either. I also have a support ticket opened and they stated that there are some issues with 4.0 and memcached that are addressed in 4.1.

Not a good news for me who is planning to upgrade to 4.0.13.1 tomorrow Any update ?

 

Unfortunately not. 4.1 should be within a couple weeks from my understanding. I'll just go with apcu until then. Page loads are still fast. 

 

Unfortunately not. 4.1 should be within a couple weeks from my understanding. I'll just go with apcu until then. Page loads are still fast. 

Good to hear at least you have one solution ;)

 

 

Good to hear at least you have one solution ;)

 

I just tested on the same server with the 4.1 beta and it worked.  

Yesterday just a few minutes later posting the message above I got exactly the same error on my test site. I am really hesitant to upgrade or not

I actually have an open ticket relating to this, opened yesterday. 

Our test site (running on the same server) has memcached running with no issue on 4.1.X but our live site running on 4.0.13.1 has the EX2 error after enabling Memcached.

Thanks @craigf136 for the feedback. I have upgraded my site a few days ago but have not enabled memcached yet after reading the comments here. Although the site's responses are acceptable I believe a healthy memcache will boost it . Looking forward to any feedback related to this if you have any. Otherwise I will have to keep the site as it is till 4.1

 

Thanks @craigf136 for the feedback. I have upgraded my site a few days ago but have not enabled memcached yet after reading the comments here. Although the site's responses are acceptable I believe a healthy memcache will boost it . Looking forward to any feedback related to this if you have any. Otherwise I will have to keep the site as it is till 4.1

@ABGenc No problem, happy to feedback what the ticket says. To be honest, I have had this issue for a while but just never got around to looking into it or raising a ticket regarding it until yesterday.

Memcache will not help a lot for IPB 3.x but it will for IPB 4.x

I had a ticket for 4.0.13.1 for the same thing. The resolution was posted above. Basically, wait until 4.1.

Basically, reply was it's fixed in 4.1 and need to wait until then.