Trouble authenticating frontend-app-authoring MFE

Hello everyone,

I have successfully mounted the course authoring MFE to my tutor docker. The docker shows that the course authoring container is running. However, I have ran into an issue. I have created a superuser using tutor but whenever I login to studio using that account, it takes me to app.local.edly.io:2001/course-authoring/home. As soon as I login, I get this axios error in the image attached. It does run for a split second where I can see the studio home but then I get the error screen. The only error I can see in the network tab has something to do with course waffle flags and analytics.min.js as shown in the image.

Additionally, I tried mounting the authn MFE and it worked absolutely fine! Made a few changes to the auth UI and faced no issues whatsoever.

Would greatly appreciate any sort of help.

Small edit: The authentication works now and I can access the studio. But I get the same error once I click on create course after adding all the relevant course info

@Suleman_Hamdani

Welcome to the forum. We will need more information regarding this. Can you tail the cms logs while you try to access studio.


$ tutor {dev/local} logs cms -f

This will help you see the logs for cms and then try to access the studio, what I am assuming is there will be some error on cms side of platform and if I am right there might be some un-applied migrations if that is the case you can exec in the shell.

tutor dev exec cms bash

and then you have to apply migration by:

./manage.py cms migrate

Hi @Suleman_Hamdani,
The waffle flag endpoint is a very very recent addition. It suggests me that you are working on master instead of an open release for your MFE. Please check that your working branch is based on a release of the MFE aligned with the edx-platform release.

Thanks a lot, Andres. I was, in fact, using the master branch. I switched to openrelease/sumac and it has started to work. There were multiple open release branches here, I chose the most recent one. Haven’t faced any errors yet so I am guessing this was the right call. Thanks for your help, again!

Thank you for your reply. I was using the wrong branch while mounting the repo. It has started to work now :slight_smile:

1 Like