Hi Jean Marc, maybe look at this parameter "rgw_enable_apis", if the values you have correspond to the default (need rgw restart) : https://docs.ceph.com/en/quincy/radosgw/config-ref/#confval-rgw_enable_apis ceph config get client.rgw rgw_enable_apis ________________________________________________________ Cordialement, *David CASIER* ________________________________________________________ Le mar. 14 nov. 2023 à 11:45, Jean-Marc FONTANA <jean-marc.fontana@xxxxxxx> a écrit : > Hello everyone, > > We operate two clusters that we installed with ceph-deploy in Nautilus > version on Debian 10. We use them for external S3 storage (owncloud) and > rbd disk images.We had them upgraded to Octopus and Pacific versions on > Debian 11 and recently converted them to cephadm and upgraded to Quincy > (17.2.6). > > As we now have the orchestrator, we tried updating to 17.2.7 using the > command# ceph orch upgrade start --image quay.io/ceph/ceph:v17.2.7 > > Everything went well, both clusters work perfectly for our use, except > that the Rados gateway configuration is no longer accessible from the > dashboard with the following error messageError connecting to Object > Gateway: RGW REST API failed request with status code 404. > > We tried a few solutions found on the internet (reset rgw credentials, > restart rgw adnd mgr, reenable dashboard, ...), unsuccessfully. > > Does somebody have an idea ? > > Best regards, > > Jean-Marc Fontana > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |