API System giving 404 errors
-
Remoted with @mwarner and we were able to fix the problem.
They were accessing the api using :<url>/task/current when it should’ve been :<url>/fog/task/current.
The confusion came because they weren’t expecting to need the /fog portion as they allow the :<url> to go directly to the fog gui.
-
You think it’s safe to solve this now?
-
The examples I posted do have the /fog directory included in them.
-
@Tom-Elliott Yes it is safe to solve now, sorry for the delay. Thanks again!