-
Notifications
You must be signed in to change notification settings - Fork 204
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
YAML import not working? #377
Comments
Looks like the API is not accessible in the Docker Compose build. I'm getting the same error with a CSV file. In the server logs it looks like this:
|
@stijnb1234 I just tried to import some random YAML file with our standard docker-compose file (https://github.com/ever-co/ever-traduora/blob/develop/docker-compose.yaml), and it all worked for me. @loleg , not sure, for me, API request worked; see below:
|
☝️ Thanks. I've opened a separate issue since my problem is a CSV and even more specifically, English. |
I have the same issue when I want to import a PO file. I tried hosting the Docker container on a Linux and on a Windows host, same error on both machines. The only change I made to the compose file is adding a database password and to add a volume for the mysql data. Is there any way to get more information what is happening? Log file, etc.? Edit: I also tried to use the docker-compose file without any changes, same issue. |
@mmttim well, if you run it in docker, you can ssh to it, run API manually in console and see all output and most probably you should see why / where it failing and see error message etc. Not different to any other NodeJs app running inside Docker container honestly. |
I had this issue as well with CSV. It took me a while to realized that if there are entries duplicated in the CSV you will get that error... Not very useful message to be honest. |
Describe the bug
I'm trying to import a yaml file, but I get: "Error, resource not found"
To Reproduce
Expected behavior
It should just import
Screenshots
Environment (please complete the following information):
latest
Additional context
My docker-compose.yaml file (created in Portainer):
(I've connected it to another network too, so that I can proxy it to my subdomain)
The text was updated successfully, but these errors were encountered: