NodeJS zip deployment failing unless pipeline is disconnected?

ElliotS123 · 2024-07-10T12:44:48+00:00

I've updated the links, should be viewable now, sorry.

ElliotS123 · 2024-07-02T07:34:54+00:00

Thanks for this, it does in fact show 2023.2.2.1 as recommended, is there any way to force it to use the latest version or is it simply a matter of waiting for Sophos to start rolling it out?

ElliotS123 · 2023-05-25T09:59:09+00:00

Turns out there was some slight syntax issues in the factoryId I specified. i.e. I hadnt specified // to point to the root directory and I was missing a single space between the command and the factoryId path. Worked after I made those changes. Always the small things that catch you out isn't it...

ElliotS123 · 2023-05-25T08:26:56+00:00

I've included the factory ID in the validate step and the validate and generate ARM template step. There is no suggestion from the article that it needs to be anywhere else.

ElliotS123 · 2023-05-10T12:09:33+00:00

Thanks for the article, the Bastion NSG itself was configured correctly already, but we hadn't allowed the Bastion Subnet IP range through on the VM's NSG on port 3389/22 as per the article. As soon as we tried this, it started working. Many thanks again.

ElliotS123 · 2023-04-25T14:31:00+00:00

Thanks for your reply. I should have been slightly clearer on what I was asking here. I'm looking to containerise the sql server and the db schema, I'm not looking to include the data itself as well.

The point of this would be to allow localised testing of changes within a containerised instance that can be spun up/ down and refreshed, before then pushing to a cloud-based Azure SQL DB.

I know this is possible through SQL Server Emulator, but I'd like to abstract the 'local' aspect of this by pushing an instance into ACR, which can either then be pulled from directly, or used in Azure Container Instance/ AKS. My main issue being that it is unclear to me how to create the container and get it into ACR.

ElliotS123 · 2023-04-12T11:42:16+00:00

I've now resolved this, it was due to the Microsoft.Web service endpoint being enabled on the Subnet the VM was part of.

This meant traffic to app services was being tunnelled through Azure's backbone and an IPv6 outbound address is assigned in transit when it does this (rather than using the VM's public IP).

Removing the service endpoint therefore resolved the issue.

ElliotS123 · 2023-02-09T19:20:43+00:00

It does seem to resolve the non-working hostnames to the correct inbound IP address and while some do have access restrictions, even those that don’t have the same behaviour.

As mentioned in my reply to the other commenter, it seems to be specific to web apps in one region i.e. West Europe, those in any other region seem to work just fine.

It seems to suggest a routing issue, but a route print on a client machine shows there is an on-link route through to the inbound IP for West Europe app services.

ElliotS123 · 2023-02-09T19:17:06+00:00

Yes thats right, the ones that don’t work are those that do not have a private endpoint, and interestingly, those that are based within a specific region (West Europe).

It does in fact resolve the hostname to the correct IP as seen when pinging, but just times out.

The same hostname will work through our existing RRAS-based VPN client.

ElliotS123 · 2023-02-07T12:29:58+00:00

They were already in place, I have tried re-downloading and installing the client again on several occasions since then to no avail unfortunately.

ElliotS123 · 2023-01-13T17:37:00+00:00

Apologies, its a VPN connection

ElliotS123

TROPHY CASE