Various issues

[rawaa123]

Since last week, we are experiencing many problems with CourseMapper.
We are not able to upload and delete a material, or generate a Knowledge graph.
The issue with material uploading is that its created on the front end but the PDF is not stored in the backend. So when we try to retrieve it, we can not and it appears blank on the screen with an error '404 not found'. Thats why we are not able to delete it as well because it does not exists. Is there anything changes in the server? the file upload location or URL that is hindering the frontend access the db and store it there?

2. Moreover, When creating Knowledge graph locally we faced an issue of not being able to connect to 'dbpedia-spotlight-en.soco.inko.cloud', is this URL changed as well?
3. These days, It's not deterministic, sometimes all the courses just don't appear, and after some time or refreshing a few times, with luck they might appear.
4. We were not able to access Argo as well but then I have noticed that you made some changes to the URL 7 days ago. No changes from our side have been pushed since long time.
   Could you please help us to figure out what the problem is? is it related to the URL changes, or something is changed at the server side?

[ralf-berger]

Yes, all subdomains of inko.cloud were changed to ude.systems. The host dbpedia-spotlight-en.soco.inko.cloud doesn't appear anywhere in any deployment configuration though. Seems to be hardcoded as a default in coursemapper-kg/concept-map/src/config.py and wasn't added to neither Compose nor K8s config.

[rawaa123]

Since last week, we are experiencing many problems with CourseMapper.
We are not able to upload and delete a material, or generate a Knowledge graph.
The issue with material uploading is that its created on the front end but the PDF is not stored in the backend. So when we try to retrieve it, we can not and it appears blank on the screen with an error '404 not found'. Thats why we are not able to delete it as well because it does not exists. Is there anything changes in the server? the file upload location or URL that is hindering the frontend access the db and store it there?

This point has not solved. Only the solution related to the 2nd and 4th points? what about the 1 and 3?

The issue with material uploading is that its created on the front end but the PDF is not stored in the backend Webserver. This path: /webserver/public/uploads/pdfs.

I need to remention No changes from our side have been pushed since long time. and the issue is only since last week

[ralf-berger]

@rawaa123 I identified two seemingly unrelated topics in your text, please see the associated issues and PRs.