I have an Azure Redis Cache instance which is up and running. I would like the redis server to receive data from a non-local network, such as my web server. For example, I want to access the redis server via PHP from my web server via $redis->connect. But here I am getting Connection refused . I read on Stackoverflow that I should change bind 127.0.0.1 to bind 0.0.0.0 such that the server will listen to non-local requests. However, I cannot find this property in my Azure portal. How can I achieve this?

UPDATE 2024-01-09: Cause turned out to be hosting provider was not allowing access to port 6379. Below is comment from Tobias: So it turns out that my hosting provider is not providing access to port 6379. That is why it kept failing. Thank you all for your comments and help. Hi Tobias, Please enable public network access if you haven't already. You do this on Private endpoint blade, as shown below: Once above is done (give it a minute to take effect), any IP is allowed by default, unless you create a rule on Firewall blade. For testing you might want to delete any firewall rules, click Save, wait 1 minute, and verify it works. Once it is working, create a firewall rule for your web server public IP and test again to make sure it still works. Please click Accept Answer and upvote if the above was helpful. If you still need assistance add a comment below with your pricing tier, network option you selected during creation (public, private endpoint, vnet), and other networking details if relevant. Thanks. -TP

Connect to Azure Redis Cache from non-local network

Accepted answer

TP 98,811 Reputation points

2024-01-01T09:39:33.0266667+00:00

UPDATE 2024-01-09: Cause turned out to be hosting provider was not allowing access to port 6379. Below is comment from Tobias:

So it turns out that my hosting provider is not providing access to port 6379. That is why it kept failing. Thank you all for your comments and help.

Hi Tobias,

Please enable public network access if you haven't already. You do this on Private endpoint blade, as shown below:

Once above is done (give it a minute to take effect), any IP is allowed by default, unless you create a rule on Firewall blade. For testing you might want to delete any firewall rules, click Save, wait 1 minute, and verify it works. Once it is working, create a firewall rule for your web server public IP and test again to make sure it still works.

Please click Accept Answer and upvote if the above was helpful. If you still need assistance add a comment below with your pricing tier, network option you selected during creation (public, private endpoint, vnet), and other networking details if relevant.

Thanks.

-TP
Please sign in to rate this answer.

2 people found this answer helpful.
Tobias Widmer 20 Reputation points

2024-01-01T10:22:31.78+00:00

Thanks for the response. However, I don't see the option "Enable public access". See here:

Notice that I use Redis under the Microsoft Azure Sponsorship. The status reads: Running - Standard 2.5 GB.

Thanks for any hints.

TP 98,811 Reputation points

2024-01-01T10:27:42.0033333+00:00

Okay, you're on Standard C2 tier. When you created it, which option did you choose on Networking tab (public or private)?

Where is your web server running? Is it on VNet in Azure, or Azure App Service, or outside hosting (non-Azure) provider, something else?

Tobias Widmer 20 Reputation points

2024-01-01T11:21:10.25+00:00

I can't remember what networking tab I chose...

My web server is a non-Azure provider (outside managed hosing). However, I have already talked to my provider. They have no problem pinging the Redis Cache from there server.

TP 98,811 Reputation points

2024-01-01T12:10:05.98+00:00

I'm guessing you chose public, or if you did choose private, you already clicked the button to enable public access (button disappears after it has been enabled).

When you attempt to connect, are you using TLS (port 6380), with code that supports TLS? Or are you trying to connect using non-TLS (port 6379)? The default if you created it from the portal is not to allow non-TLS port unless you checked the option on the Advanced tab.

If you are trying to connect using non-TLS you have to set Allow access only via SSL to No on Advanced settings blade and save your change. It isn't recommended to allow non-TLS for security reasons.

You can check on Overview blade which Ports are enabled.

Tobias Widmer 20 Reputation points

2024-01-01T13:36:16.44+00:00

I am trying to connect Redis Cache from my Wordpress site. So I followed this instruction:

https://techcommunity.microsoft.com/t5/apps-on-azure-blog/distributed-caching-with-azure-redis-to-boost-your-wordpress/ba-p/3974605

There, it says that I must select No for Allow access only via SSL.

That's what I did. So I am trying to connect via Port 6379. In the Azure Portal, I have activated this Port. So on the Overview page, it says: Non-SSL port (6379) enabled.

In order to test connection, I use this PHP script:

<?php $redisHost = 'himmlischesjerusalem.redis.cache.windows.net'; $redisPort = 6379; $redis = new Redis(); try { $redis->connect($redisHost, $redisPort); $redis->auth('my_primary_key'); echo 'Connected to Redis successfully!'; } catch (Exception $e) { echo 'Failed to connect to Redis. Error: ' . $e->getMessage(); } ?>

This PHP is executed on my webserver and returns Connection refused.

TP 98,811 Reputation points

2024-01-02T10:35:45.54+00:00

I just did test. Created Azure Cache for Redis with non-TLS port enabled, copy/pasted your code to my local machine, changed host and primary key, saved as connect.php. Ran it using php.exe and got "Connected to Redis successfully!"

As a test, please create a new Azure Cache for Redis with Basic C0 SKU with non-TLS port enabled in new resource group, and see if you are able to connect to it. Perhaps test your code from your local machine as well as your web server to see if there is any difference in the results.

Once you have finished testing delete the resource group so that charges won't keep accruing.

Tobias Widmer 20 Reputation points

2024-01-02T12:36:01.6833333+00:00

I have created a new instance with Basic C0. I can PING the instance usnig my locally installed redis.cli without any problems. However, if I execute the php on my webserver, I get Connection refused. I really puzzled. Perhaps I should give you access to my credentials so you can check for yourself.

GeethaThatipatri-MSFT 29,477 Reputation points Microsoft Employee

2024-01-04T16:28:00.3733333+00:00

@Tobias Widmer could you try connecting differently via connection string, which contains more information than just host, port, and key? I suspect you need to specify SSL=false somewhere in the connection, else we default to SSL=true, which is not for port 6379.

Regards

Geetha

TP 98,811 Reputation points

2024-01-05T09:38:56.2366667+00:00

@Tobias Widmer Did you try to execute the php code from your local PC? I would like you to test from different machine and network that isn't related to your hosted web server at all.

One detail that is interesting (for troubleshooting purposes) is that you get Connection refused. Reason it is interesting is that isn't what I would expect--it should time out instead. For example, if I disable non-TLS port or I create firewall rule so that my IP address isn't allowed, attempt to connect, it times out.

If you want to create another Basic C0 with non-TLS port enabled, have me test connecting to it using host and primary key, I can do that. You would need to give me general time range (so that you can delete it after I test to keep costs at minimum), and I can give you instructions on providing primary key to me.

If you test the php snippet from your local PC and it succeeds then there would be no need for me to test.

Tobias Widmer 20 Reputation points

2024-01-05T15:28:10.3533333+00:00

@TP: Thank you very much for your help.

I tested my php snippet from my local PC and it succeeds indeed. I can connect without any problems. But once I copy that same snippet to my webserver, it gives me Connection refused. My hosting provider told me that they tested the connection via telnet and confirmed that access if provided (it is not blocked in any way).

I remember that in the beginning, when I first tested it, I also got a timeout. But now it's Connection refused. I may have changed something but I can't remember what it was... :-(

In any case, I can ping locally but I cannot from my webserver.

TP 98,811 Reputation points

2024-01-05T16:48:31.33+00:00

Okay, off the top of my head. If your server is a VM is there any firewall/security software enabled on it that could be blocking outgoing requests?

Another thing, do you have a different version of php on the webserver than what you tested with locally?

Did your hosting provider test by first connecting (via RDP/SSH) into your webserver and then trying to telnet to Azure Cache for Redis port?

Tobias Widmer 20 Reputation points

2024-01-09T17:17:33.82+00:00

So it turns out that my hosting provider is not providing access to port 6379. That is why it kept failing. Thank you all for your comments and help.

TP 98,811 Reputation points

2024-01-09T17:26:25.9766667+00:00

@Tobias Widmer Please click Accept Answer to close up this thread.

Thank you.

Samuel Segbornya Kodzo Adranyi 0 Reputation points MVP

2024-05-07T18:47:35.44+00:00

Enable public Network access no longer shows.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Connect to Azure Redis Cache from non-local network

0 additional answers

Your answer