Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/api/v1/openvpn/csc Error 404 #251

Closed
advancedluser opened this issue Jun 24, 2022 · 2 comments · Fixed by #248
Closed

/api/v1/openvpn/csc Error 404 #251

advancedluser opened this issue Jun 24, 2022 · 2 comments · Fixed by #248
Labels
documentation Improvements or additions to documentation

Comments

@advancedluser
Copy link

When I try to GET or POST with curl, or from the api/documentation page, I am getting the following error:
`

<title>404 Not Found</title>

404 Not Found


nginx `

And basically the same with curl:
curl -k -H "Authorization: xxxxxxxx xxxxxx" -H "Content-Type: application/json" -X GET https://xxxxxx:xxxx/api/v1/openvpn/csc -d @post_csc.json
`

<title>404 Not Found</title>

404 Not Found


nginx `

The other GET and POST requests that I used so far worked. What could be the issue? Am I doing something wrong?

pfSense Version & Package Version:

  • pfSense Version: 2.6.0
  • Package Version: 1.4.2

Affected Endpoints:

  • URL: /api/v1/openvpn/csc
@jaredhendrickson13 jaredhendrickson13 added the documentation Improvements or additions to documentation label Jun 24, 2022
@jaredhendrickson13
Copy link
Owner

Looks like this is a documentation discrepancy. The endpoint URL is actually /api/v1/services/openvpn/csc.

I'll correct that in the next release branch.

Thanks!

@jaredhendrickson13 jaredhendrickson13 linked a pull request Jun 24, 2022 that will close this issue
@advancedluser
Copy link
Author

Thank you very much for the fast reply @jaredhendrickson13, works now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants