#Self Hosting Error Cannot Create Default Account
1 messages · Page 1 of 1 (latest)
Heyy 👋 Any erros in docker compose logs appwrite?
You are faster than me now 🤣
[Error] Timestamp: 2025-05-23T20:45:21+00:00
appwrite | [Error] Method:
appwrite | [Error] URL: /favicon.ico
appwrite | [Error] Type: Appwrite\Extend\Exception
appwrite | [Error] Message: Route not found. Please ensure the endpoint is configured correctly and that the API route is valid for this SDK version. Refer to the API docs for more details.
appwrite | [Error] File: /usr/src/code/app/controllers/general.php
appwrite | [Error] Line: 1583```
Interesting 🤔 What steps did you follow when setting up Appwrite locally?
ran this
docker run -it --rm --volume /var/run/docker.sock:/var/run/docker.sock --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw --entrypoint="install" appwrite/appwrite:1.7.2
set default port to something not 80 since i run other services on here
and then went to the login page to sign up for an account
Got it. All sounds correct.
Let's investigate further.
After trying to login/sign up, if you open browser's Console, can you provide a screenshot?
In "Network" tab, can you find the specific request, and show details of that? (payload, response, headers, path..)
yeah
hmm, lets see.. What URL exactly is blocked by CORS?
I am guessing something like http://localhost/v1/account
yes
perfect. if you visit it manually (in new browser tab), what does it respond with?
Oh wait, is it not localhost:[some-port]? 🤔
gives me a 404
and yes
Can you send me the response body? Just want to make sure this is 100% appwrite response
(if not, we know problem is before appwrite api container)
oh, just empty 404?
This looks like it’s the same issue I’m having that I just posted here https://discord.com/channels/564160730845151244/1375547722245083286
I would expect something like this, for example
{"message":"User (role: guests) missing scope (account)","code":401,"type":"general_unauthorized_scope","version":"1.7.2"}
Oh wow, sounds easy to reproduce. Let me spin up droplet to try it
There might be new security measures due to sites, which might be causing trouble for when port is customized.
Trying on my end, Ill get back to you folks in 5-10 mins
just read ur issue and yeah saw the reply . . . non standard ports are an issue huh
i need 80 open as i use it for other stuffs
only other option i guess would be to host on an actual vm
@winged badge out of curiosity, what OS are you using?
ubuntu
Oh never mind. I’m on a Mac. Was hoping there was some connection with Mac and silicon chips here. Guess not
nah . . . me thinks its attempting to use the default port for requests despite the fact that there is a different one in there
Yup, that’s what I think as well
only reason why it would be pulling a CORS error
if u take a look at network anything that is not a direct asset is pulled without the port and fails
interestingly enough i had used a 1.6 version previously without this problem so seems to be a new issue in regards to 1.7
Found it, trying to see if there is a fix other than 1.7.3 release
we gotta wait for 1.7.3? or can we just pull that for the docker instance and remove the 1.7.2
I am trying to find solution that doesntrequire 1.7.3. Need another 5-10mins
i should say is it a current version or one in a beta or something
ight . . . thanks for helping me out with this . . . im sure many others will thank u as well if they come across it for this thread
of course i say that and i didnt even look at literally the one prior to mine
Grrr, it's so complex. And for us it's just 1 line fix
Let me try to reach some engineers for reviews
On Friday night
# Clone Console
git clone --single-branch --branch 6.0.8 https://github.com/appwrite/console.git
# Enter directory
cd console
# Build new image
# Took me ~3mins
PUBLIC_APPWRITE_ENDPOINT="http://localhost:9555/" docker build -t appwrite/console:6.0.8 .
# Go back to Appwrite folder
cd ..
# Restart Appwrite
docker compose up -d --force-recreate
This, probably
but its just so complex I didnt even want to suggest it
if its literally just run that then how is it complex?
ill try it in a minute and see if it works
one question though
that endpoint should i be using my own port instead of 9555?
ah, yes, exactly. change port number, I was testing on 9555
We consider this complex 😅 Simplicity is core value of Appwrite
should i bring down appwrite before doing it?
or will it just refresh it automatically
I got PR ready, checking with engineers now. You can give it a comment too https://github.com/appwrite/console/pull/1883
Last command is to restart stuff
very good values to have
my boss complains i dont follow KISS principle enough myself
soooo . . . should the git clone only happen within the appwrite folder itself and not an outside directory?
idk if that matters with docker as i dont really use it much for anything
Doesnt matter, buuut give me a minute. We might not need these steps all-together
Enjoy your favourite song, or two, and Ill get back to you
i did it outside and nothing . . .
nope
still issues
continues to pull from default port
@winged badge Good news! I managed to get PR merged, and release new version. Please do following:
-
Open
docker.compose.ymlfile (auto-generated inappwritefolder, created by installation) -
Locate
appwrite-consoleservice, it should be using imageappwrite/console:6.0.8(or maybe a bit different number) -
Set image version to
appwrite/console:6.0.11 -
Save changes
-
Apply changes with
docker compose down && docker compose up -d -
Enjoy Appwrite on custom port 🥳
Please let me know if this works for you 🙏
Great work on Friday night!
WE HAVE LIFE!!!!
thanks u very much . . . that is some good stuffs this late in the day
Happy to help! 🙌
In case you face further issues, let's switch back to #🏠│general , or a new #1072905050399191082 thread.
Doing so will allow us to keep this thread strignt to the point, for anyone facing the same.