Unable to use docker-compose.yml - is there a branch with a stable version?

[PiotrNowara]

Hi,

it looks like images from the main branch docker-compose.yml are not available:
docker-compose up [+] Running 2/2 ✘ webprotege-gwt-api-gateway Error 1.8s ✘ nginx Error 1.8s Error response from daemon: manifest for protegeproject/webprotege-nginx:1.2.1 not found: manifest unknown: manifest unknown

Can you point out a stable branch/config? I'm planning to use WebProtege in an important project and noticed those issues when working on previous docker-compose.yml I cloned a couple of weeks ago:

1. I was getting a random(?) 504 errors when using web UI
2. I was not able to download the ontology project file from the main panel (the download didn't seem to start at all, but there were not errors in logs).

Thanks for any help,
Piotr Nowara

[alexsilaghi]

Hello ! . The issue is that the latest version of nginx is not released yet . you can release it yourself using the command : "docker build -t protegeproject/webprotege-nginx:1.2.1 ." in the nginx folder . Also unfortunately the ontology download is not working currently.

[PiotrNowara]

Thanks for answering so quickly! Is there any workaround for the ontology download issue? Can I download it via some different API call? czw., 10 kwi 2025 o 12:41 alexsilaghi ***@***.***> napisał(a):

…

Hello ! . The issue is that the latest version of nginx is not released yet . you can release it yourself using the command : "docker build -t protegeproject/webprotege-nginx:1.2.1 ." . Also unfortunately the ontology download is not working currently. — Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGEDKJMEMFFOGAV3QN4IRPD2YZDEHAVCNFSM6AAAAAB23E42QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJSGMYTQNZUGI> . You are receiving this because you authored the thread.Message ID: ***@***.***> *alexsilaghi* left a comment (protegeproject/webprotege-deploy#35) <#35 (comment)> Hello ! . The issue is that the latest version of nginx is not released yet . you can release it yourself using the command : "docker build -t protegeproject/webprotege-nginx:1.2.1 ." . Also unfortunately the ontology download is not working currently. — Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGEDKJMEMFFOGAV3QN4IRPD2YZDEHAVCNFSM6AAAAAB23E42QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJSGMYTQNZUGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[alexsilaghi]

All ontologies are stored as owl files inside a docker managed volume , if you want to access them , change in the docker-compose file the volume from :
volumes:
- webprotege-data-directory:/srv/webprotege

to something like

volumes:
- /srv/webprotege:/srv/webprotege (now all ontologies will be placed in your drive where you download the project under path /srv/webprotege) . The download feature only provides a zip , but the zip contains the same .owl files that otherwise you would access from that path. Also if you just pulled the project , there won't be any ontologies 😄

[PiotrNowara]

I can access the /srv/webprotege folders but don't see any OWL files there. In the data-store/project-data subfolders there are only changelogs files. Are you sure OWL files should be located there?

[alexsilaghi]

yes, but first you must create a project in order to generate an ontology . If you don't see the "Create project" button when you reach the landing page then you don't have the permissions. Have you set up the webprotege realm in keycloak?

[PiotrNowara]

Yes, I created users in Keycloak and can use the "Create project" button. I even uploaded the entire HPO ontology (more tha 72MB). I can edit it without problems but don't see any OWL files.

[scottrbrtsn]

Hi, is there a place which captures the status of webprotege v5? Like a centralized issue board?

Is it stable enough to use at all? I understand some features might be lost, but it's not obvious what to expect.

My primary issue is the UI doesn't seem to be able to connect to the gateway as a websocket and I cannot tell if I misconfigured things or if the system is truly unusable.

Is it possible someone could update the wiki which hasn't been updated since Mar 18, 2022 or start updating the READMEs for each repo so others have some glimpse into known issues.

[manuel-j-diaz]

Hi, @alexsilaghi . Chiming in on this issue, specifically the need for a stable version.

I'm using WSL2 (Ubuntu 24.04). I followed the write-up, however, protegeproject/webprotege-nginx:1.2.2 and protegeproject/webprotege-event-history-service:2.0.0 are the only images not available for AMD64. Instead, I had to build the nginx image as stated in #35 (comment) and bump the webprotege-event-history-service tag to 2.0.23-who. That got the stack up and running.

Then, I made the Keycloak realm and registered my local user. I can open a browser and log-in but do not see the "Create project" button:

As per #35 (comment) , it is a permissions issue, but how can I fix it? I made no changes to keycloak/webprotege.json. I can't see an error in any of the services' logs, but happy to provide any. FWIW, here is my user's permissions in Keycloak

Also, some observations/suggestions:

• I couldn't change the Local Host Resolution to something other than webprotege-local.edu. Maybe it is because there's a mix of hard-coded webprotege-local.edu in the docker-compose.yml and keycloak's webprotege.json ? Please consider future stable versions to allow users to specify a custom LHR.
• Just like how Keycloak is accessible via localhost:8080 via the host's browser, it would be nice to be able to access the webprotege GUI via the host's browser on localhost:8088 (or similar port) for WSL deployments instead of opening a browser window within WSL.

Commit: 09e6de8

[manuel-j-diaz]

Fixes that worked for me:

After the service mesh is running and I created the Keycloak realm, I noticed my user had realm-level roles, but not client-level that WebProtege needs. I found that by the browser console:

13:03:36 GMT-500 2025 ReadLoggedInUserInitializationTask
INFO: [ReadLoggedInUserInitializationTask] set logged user: 
GetAuthenticatedUserDetailsResult{userDetails=UserDetails{UserId{mjdiaz}, displayName=mjdiaz, emailAddress=}, 
permittedActions=[]} 

Note that blank permittedActions. So I added the client-level roles:

# log in to Keycloak
$ docker compose exec keycloak /opt/keycloak/bin/kcadm.sh config credentials --server http://localhost:8080/keycloak-admin --realm master --user admin --password password

# add client-level permissions to user
$ docker compose exec keycloak /opt/keycloak/bin/kcadm.sh add-roles -r webprotege --uusername mjdiaz --cclientid webprotege --rolename admin --rolename SystemAdmin --rolename ProjectCreator

After logging out and logging back in, the browser console shows

15:00:21 GMT-500 2025 ReadLoggedInUserInitializationTask
INFO: [ReadLoggedInUserInitializationTask] set logged user: 
GetAuthenticatedUserDetailsResult{userDetails=UserDetails{UserId{mjdiaz}, displayName=mjdiaz, emailAddress=}, 
permittedActions=[BasicCapability{CapabilityId{id=ViewAnyUserDetails}}, 
BasicCapability{CapabilityId{id=MoveAnyProjectToTrash}}, BasicCapability{CapabilityId{id=RebuildPermissions}}, 
BasicCapability{CapabilityId{id=ResetAnyUserPassword}}, BasicCapability{CapabilityId{id=EditApplicationSettings}}, 
BasicCapability{CapabilityId{id=CreateEmptyProject}}, BasicCapability{CapabilityId{id=CreateAccount}}, 
BasicCapability{CapabilityId{id=SubstituteUser}}, BasicCapability{CapabilityId{id=DeleteAnyAccount}}]}

and I can now create projects!