NGINX update breaking BAQ APIs

[chaddb (Chadd Blanchard)]

There was another post on here about Odata breaking following the change to Linux. Epicor has a NGINX config wrong. May be causing your issues.

Did API v1 of Erp.BO.PartSvc/Parts Change Over the Weekend?

So I just did a bunch of tests with an nginx Proxy proxy_pass https://myEpicor.stephengould.com; #Works Fine proxy_pass https://myEpicor.stephengould.com$uri$is_args$args; blows up erro 400, Bad Gateway (if the part has slashes) location / { set $backend "https://myEpicor.stephengould.com"; proxy_pass $backend$uri$is_args$args; } Gives a Path Undefined Error (for slash parts) 404 [image] proxy_pass https://myEpicor.stephengould.com; proxy_set_header X-Origina…

Did API v1 of Erp.BO.PartSvc/Parts Change Over the Weekend?

Thank you again, Jose. Support confirmed this is due to a misconfigured ngnix proxy.

Did API v1 of Erp.BO.PartSvc/Parts Change Over the Weekend?

The PRB is: PRB0312834

[spaceage (Chris)]

Just throwing my hat in the ring - this change messed up our HubSpot API integration. Devs figured out the new path, but how are we just changing method signatures all willy-nilly? Is there no one in charge?!?!

[chaddb (Chadd Blanchard)]

Sounds like another issue for the mega thread of Linux issues.

Linux Container Migration: Let's Consolidate the Chaos

Hey all - there are at least 10 threads floating around right now all dealing with problems that trace back (directly or indirectly) to the Linux container migration. I figured it’d be helpful to pull everything into one place so Epicor has a single thread to respond to, and so the rest of us aren’t hunting across the forum trying to find solutions. Related Threads Linux Containers Linux Containers for Cloud Can’t Edit Functions, BPMs, or Configurators MES Shortcut and Accessing MES and Kinet…

[kve (Kevin Veldman)]

Mine’s a stupid Field Security thing.

[pheim (Peter)]

So I was able to fix our apps with changing the URI to this:
https://idcspring-live.epicorsaas.com/server/api/v1/BaqSvc/{BAQNAME}(CompanyNumber)

All of my API calls are working again.

[chaddb (Chadd Blanchard)]

Think that’s what @GabeFranco was talking about too. The URLs changed at some point.

@GabeFranco

.../SaaS576/... is your production URL.

/SaaS576/ in the URL path is replaced by /server/ there, i’ve seen this issue happen in the past and it needed an epicor ticket to resolve.

[pheim (Peter)]

The whole structure changed. We went from
https://centralusdtapp07.epicorsaas.com
to
https://idcspring-live.epicorsaas.com

Some notice of this would have been nice…

[chaddb (Chadd Blanchard)]

Didn’t realize it was more than just the .../server/ part. Ooft. That must be what broke Azure AD for people then when the whole URL changed.

[Randy (Randy Stulce)]

@pheim

The whole structure changed

Our hasn’t even in Pilot. Yet???

Maybe we’re sitting on a time- here.

[pheim (Peter)]

Neither has ours. But no better place to test other than in production…

[klincecum (Kevin Lincecum)]

Both should still work.

[utaylor (Utah Taylor)]

Yeah it is. So on .14 I need to get ready to change that in azure?

[chaddb (Chadd Blanchard)]

@utaylor

So on .14 I need to get ready to change that in azure?

Not 100% sure since we aren’t cloud. But, there were some posts about needing to update your Azure SSO due to URL changes from Epicor. Let me see if I can find them. Azure is also case sensitive. So the URL configured in Azure has to match exactly what Epicor is using.

[utaylor (Utah Taylor)]

I know where to find them, thanks. Just I see conflicting statements above that “both” the old and new should work.

[chaddb (Chadd Blanchard)]

@utaylor

Just I see conflicting statements above that “both” the old and new should work.

I think that was in terms of like integrations. For SSO only the new work.

[utaylor (Utah Taylor)]

@chaddb

For SSO only the new work.

Ohhhh I see. Okay

[bderuvo (Bryan DeRuvo)]

@pheim The original url is an unfamiliar syntax to me (our education environment uses similar syntax). We’ve had our cloud environments for about 2.5 years and always had the newer format. Still on windows hosts but watching this very closely. Thanks to everyone sharing the issues.