Transport endpoint not connected

[AnderUstarroz]

I am using the following configuration to connect to my AWS cache server:

CACHES = {
    'default': {
        'BACKEND': 'django_elasticache.memcached.ElastiCache',
        'LOCATION': 'my-project.fddss4.cfg.apse2.cache.amazonaws.com:11211',
    }
}

But I am having some issues, from time to time it throws the following error:

    cache_key = get_cache_key(request, self.key_prefix, 'GET', cache=self.cache)
  File "/var/www/my-project/env/lib/python3.6/site-packages/django/utils/cache.py", line 318, in get_cache_key
    headerlist = cache.get(cache_key)
  File "/var/www/my-project/env/lib/python3.6/site-packages/django_elasticache/memcached.py", line 18, in wrapper
    return f(self, *args, **kwds)
  File "/var/www/my-project/env/lib/python3.6/site-packages/django_elasticache/memcached.py", line 108, in get
    return super(ElastiCache, self).get(*args, **kwargs)
  File "/var/www/my-project/env/lib/python3.6/site-packages/django/core/cache/backends/memcached.py", line 76, in get
    val = self._cache.get(key)
pylibmc.Error: error 26 from memcached_get(:1:views.decorators.cache.cache_): Transport endpoint is not connected

Returning HTTP Error 504 Gateway timeout

Somebody knows why is this happening?

[juanromerocortes]

@AnderUstarroz Did you solve this issue?
I've just realized I'm getting the same error in the new project.

[Iazzetta]

Check if your Memcache/Redis be in the same VPC of your ELB/EC2. Add the same security group of your EC2 in Elastic Cache.

[Anton-Shutik]

Having same issue. Look like this might be related - django-pylibmc/django-pylibmc#48