You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just spent an embarrassing amount of time trying to determine why the wsk CLI was working on one machine and not on another. The ultimate issue was that I ended up specifying the APIHOST variable as https://localhost:8443/ in the config file, with the trailing slash, which causes 404s since the CLI was sending requests to https://localhost:8443//api/v1/namespaces/_/triggers?limit=0&skip=0 (note the double-slash after the domain).
The text was updated successfully, but these errors were encountered:
Just spent an embarrassing amount of time trying to determine why the wsk CLI was working on one machine and not on another. The ultimate issue was that I ended up specifying the
APIHOST
variable ashttps://localhost:8443/
in the config file, with the trailing slash, which causes 404s since the CLI was sending requests tohttps://localhost:8443//api/v1/namespaces/_/triggers?limit=0&skip=0
(note the double-slash after the domain).The text was updated successfully, but these errors were encountered: