-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
ROOT_URL and File Not Found :( #85
Comments
|
|
Maybe the collection definition wrong?
|
|
OK, this very strange. The second started with: Both instance is absolutely identical. Everything works in the app except images. And if the first started with 3060 port, and the second with 3030, the second will works, and the first wont. |
You can access both of them now. There is english language version. You can select with flags in upper right corner. |
From my end both urls returns 404 (may it be cache on your machine?):
P.S. I'm off for today, I'll ping you tomorrow |
OK, thanks. |
OK, the problem not with FILE_URL at all. The real problem is when I restart meteor something delete all images in: |
The problem is bigger than I thought. Steps to reproduce: upload a file Now what should I do. Every restart delete all uploaded files |
It's expected behaviour, that's why I asked you multiple times to check physical file existence. |
OK, thank you. I'll try. |
Hi,
I'm afraid I don't understand using ROOT_URL in this package. Please help, what is the correct way.
Example:
When I upload images in my dev system locally with ordinary:
meteor --port 3000
everything works as expected.
But when I want to change path with ROOT_URL to access same system for testing external access with:
ROOT_URL=http://palpinter.dlinkddns.com:3000 meteor --port 3000
I receive 'File Not Found :(' error message for all uploaded images.
And if change the port only:
meteor --port 3030
the result is the same, ''File Not Found :(' for all uploaded images.
How can I change ROOT_URL to access my uploaded images?
Thx
Pal
The text was updated successfully, but these errors were encountered: