-
Notifications
You must be signed in to change notification settings - Fork 60
CSV import does not work in reverse proxy environments #194
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
Comments
Until this is fixed, a workaround for nginx users is to add a rewrite rule to the wrong # fix for plugins that don't respect proxy settings and base urls... (i.e. SpoolManager)
location ~ ^/plugin/(?<method>.*)$ {
return 307 /octoprint/plugin/$method$is_args$args;
} The QR Codes are also affected by the issue. |
Closed
OllisGit
added a commit
that referenced
this issue
Oct 24, 2021
- PR #204, #201 redesign of the Spool-Selection in the sidebar. Huge thanks to @TiziG @MarloSM - E #125 New field "Serialnumber" - E Spool selection from Edit-Dialog - E #141 New Filter: Material, Vendor and Color - E #44 Sidebar filament usage in grams instead of volume - B #199, #198, #163, #156 some QR-Code optimisations - B #197, #196, #188, #181, #178, #177, #172, #162, #142, Some UI optimisations - B #194 CSV import, behind reverse proxy - B #175 Confirm dialog not shown
Hi @hgross , Please try and give me a feedback. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The import function for CSV files does not work when octoprint is running in a reverse proxy configuration.
I could trace it down to the file upload function that seems to use the jquery
.fileupload()
convenience method. Thesubmit()
call does not respect the base uri of the api client.My octoprint is behind a nginx reverse proxy at

/octoprint
. Therefore the correct path for the file upload should be/octoprint/plugin/SpoolManager/importCSV
but/plugin/SpoolManager/importCSV
is used.At first I assumed my input data is invalid, since i converted it from the FilamentManager database, but it does not even arrive on the backend.
This is the UI when the upload fails:

The baseUrl parameter of

self.apiClient
looks correct in the debugger:The text was updated successfully, but these errors were encountered: