cors currently turned off
When CORS is disabled you will indeed get that error, is the error the same after you enabled it? Also check in the admin panel if CORS is enabled there.
Been searching in forums and all topics has :8080 in the request instead only “localhost”.
Something about it? Sorry I’m just thinking.
cors is enabled and have re-deployed
i do NOT have those additional settings in the admin console
For info, i have tried same setup on a win 10 system (currently on win 11) with beta 1 and am seeing exactly the same CORS issue.
Could it be if CORS is disabled then re-enabled it is not re-enabling correctly?
is there a json file i can check to see if the config is correct?
I have MANUALLY added those missing CORS entries via the Admin panel and that seems to have fixed the issue, could it be that when deleting CORS they are removed but when re-enabling they are not re-added?? Just an idea, you’re the expert!
I don’t know when it happens, tested with disabling via admin and in Wappler, in both cases the settings were not removed when disabled.
At least we have a simple fix if others have this issue, very useful to be able to add new options from the couch admin screen
What specifically would I do to fix the CORS issue for myself with Beta 1?
OK, assuming you know how to use the CouchDB admin console as shown in my video
When i viewed the CORS section i saw the following single key under the cors section of the settings
From the admin CouchDB console i simply manually added the missing keys, credentials, headers and methods which were present in patrick’s system
which can be done from the admin panel as I show in the video here
1 Like
Outstanding! Mil Gracias!
1 Like
How, what did you change?
I have removed and rebuilt the cloud database containers a number of times trying to resolve the below bug.
Sorry, i am unsure exactly when the cors entries disappeared during that process. The above fix worked again though.
It appears that in some cases, when the couch datbase is defined, that the CORS entries are not added.
I also notice the message “Adding Cors …” remains for quite a long time (can be minutes) which leads me to believe that there is an issue with that addition, perhaps the task failing
Are you working on a remote target and not locally with Docker Desktop maybe?
no, local at present