#Static IP to Azure functions

1 messages · Page 1 of 1 (latest)

brisk mason
#

we have a set of few azure functions and we have a public IP address which has been whitelisted by our client already.. so is there a way I can assign that ip address to our azure functions ?

unborn garden
brisk mason
#

Thanks Rowan for the reply. Yes the above link helps , but unfortunately our function app is on consumption plan (the above link works only for Premium plan or in a Dedicated (App Service) plan), So as a work around, we added a custom domain in Functions app and resolved to the required IP ... Anyway thanks for your time @unborn garden

unborn garden
#

Glad you were able to sort it!!

brisk mason
#

@unborn garden Similar to the above, can we set static IP for azure container app? any idea on this ?

unborn garden
#

Hey, yeah you absolutely can do this! I think you need to have a virtual network to manage the IP, I'll see if I can fit in time today to try it out. I needed to do this a while ago myself but didn't have time for my use case (like literally I had an hour before the container app had to be used, and it was only used for 2 hours), so I'm interested in actually giving it a shot.

brisk mason
#

Thanks @unborn garden Please let me know if you get any breakthrough in this

unborn garden
brisk mason
#

@unborn garden Thank you so much for your time to make these video. Yes it really helps. Expecting more videos from you in future.

unborn garden
#

I'm really happy it helped! Glad you enjoyed the video too 🙂 If there's anything else you need help with, feel free to reach out!

brisk mason
#

@unborn garden, Everything is setup as per your tutorial, In the Application gateway section , I am getting the following error

10.0.1.4 (static-pool) 80 (routingsettings) Http Unhealthy Received invalid status code: 404 in the backend server’s HTTP response. As per the health probe configuration, 200-399 is the acceptable status code. Either modify probe configuration or resolve backend issues. To learn more visit - https://aka.ms/StatusCodeMismatch.

unborn garden
#

At which part does this pop up in the gateway section?

#

Also, does the IP match the private one exactly on your container instance, it may have set up differently, mine were just defaults, so if you've done anything extra/different there might be slight differences in the IP perhaps?

brisk mason
#

Ip I copied from container instance

unborn garden
#

This might sound really basic, but have you tried waiting a few minutes and trying again? Sometimes container based implementations fail because there's stuff Azure does behind the scenes with the setup, even after it says it's finished.

Was there anything different you had to do from the video due to the requirements you had? I'd like to recreate the issue in my setup if possible.

#

Also, I'm not sure where it makes a difference, but I believe there's a requirement for certain resources here to live in the same deployment region. I would typically always advocate for this anyway, unless you have a good reason not to.

#

Another thing to check: I feel like it shouldn't care at this point what your container is doing, but does your containerised application have something open on port 80/ is the container itself set to http, rather than https?

brisk mason
#

No, the video was perfect. I could easily follow the steps and complete the setup. When I was about to test , I got this warning popup on app gateway. So figuring out what might be the issue ...

brisk mason
unborn garden
brisk mason
unborn garden
#

Awesome, I'm going to take a look too throughout the stuff I have to do today too, and see if I can come up with a solution for you!

unborn garden
#

Just to check, did you make sure the app was reachable from it's public IP too, just to make sure it's working?

brisk mason
#

Can we enable public IP access once it is created? Right now no public address is showing up.

#

Or shall i recreate it?

unborn garden
#

hmmm, it should be enabled and show up as soon as you create it, it should require it when you set the application gateway up. Perhaps this is something that might have been created in the wrong region?

#

Oh also perhaps the Tier could make a difference, sometimes Azure hides certain functionality behind tiers. If you left all default then I know it works fine (because that's what I did)

#

aaaaah I see, your app has a FQDN I'm guessing? The link you first sent me should help solve the problem if that's the case. If this is the case and you can't find where you apply that, just let me know and I can figure it out by adding a FQDN to my container and doing it again 🙂

brisk mason
#

Ok Ok Even I am recreating gateway from beginning just to rule out any misconfigurations..

unborn garden
#

cool cool, let me know how it goes!

brisk mason
unborn garden
#

Hey, so sorry, didn't see your message until super late Friday. From my experience, if it's returning "Invalid" it sounds like the Azure part is working, and the app itself is having a problem. Is it just the base weatherforecast you're using, or has it been modified?

brisk mason
#

Yes Rowan, There was an issue with App , Default Routing was not enabled in the app and it was returning 404 error when we give the IP to backendpool .. Now I made it proper , and it is working now... Thank you so much for the help 🙂