Since i upgraded to 1.4.0 and then 1.4.1 , i can no longer access the console using http://127.0.0.1 instead i have to use http://localhost instead. Also since i am writing a mobile app and the appwrite runs on docker and the ip is NAT ed to the host machine , i can no longer use http://MY_HOST_IP/v1 to access the api from my client app. All the above was previously working on 1.3.8.
How can i fix this ?
Can you not use localhost instead?
@Joshi yes i could but what about the client app i am developping? normally there is a natural NAT from localhost to the host machine's ip but in the new version this is no longer working. i can do with using localhost for accessing the console.But for my frontend it is a huge problem
I'm surprised 127.0.0.1 and localhost are considered interchangeably
They are considered the same thing
@Joshi indeed they are the same but unfortunately for me that is how i described above let me show you with some screenshots
@Joshi when accessing http://127.0.0.1 in the browser
@Joshihere is a shot with using localhost instead
here is the error message when trying to call the endpoint <h1 class="heading-level-4 u-trim-1">Error 500</h1> <p class="text">Domain environment variables not configured. Please configure domain environment variables before using Appwrite outside of localhost.</p>
I have the same issue as you
@Steven Hi Steven pls can you see the above screenshots for this issue I have
yep. this is as expected. you should be using localhost. if you need to use an IP, you'll have to update the domain env vars with that IP address
@Steven but is this an intended change? I mean I could use either 127.0.0.1 or localhost regardless with 1.3.8...Also when calling the endpoint even with localhost instead of the ip I get the error listed above
This one here is the error message when trying to call the endpoint <h1 class="heading-level-4 u-trim-1">Error 500</h1> <p class="text">Domain environment variables not configured. Please configure domain environment variables before using Appwrite outside of localhost.</p> ``
previously, you could use ip address to access the console. in 1.4, that's been limited because of routing and to help prevent spoofing/phishing
yep, do as it says
@Steven ok I understand better now. I'll do it and hopefully be able to access the Api...I'll revert here 🙏. Great work and congrats for the awesome work you guys do and for the 1.4 release
[SOLVED] 127.0.0.1 no longer accessible on self hosted appwrite 1.4
Recommended threads
- Push Notification FCM Error
Hello dear people. I tried to integrate Push Notifications into my Flutter App. Everything works fine on Android/iOS Simulator + Testflight but as soon as I s...
- Skip total counts crash the query
Hello, When adding the total parameter (either true, the default, or false) to the listRows function, it raises the following error: `type 'bool' is not a sub...
- appwrite free plan resources issue
i'm on free plan and i just used 700MB bandwidth with 8mb storage and 141k requests, but when i'm trying to continue developing my app it send me an error messa...