How to set up describe service with https?

Hi, I’ve already configured my SPARQL endpoint over https with en external signed certificate.

I’d like to do the same for the faceted browser and describe services.

In Web Services, I added an entry.
Then, I’ve added an entry in Web Application Server :

and I copied the rewriting rules from the domain:

Now I try to reach it using https:

but I get an error in my browser: “The requested active content cannot be displayed due to execution restriction”.

although the the http query works fine:

What did I miss? Thanks in advance for your help.


As a complement, here is the config of the web service:

And here are the rewriting rules:

Can you please confirm if you are using Virtuoso open source or commercial ?

Did you configure the HTTPS listener before installing the Facet Browser VAD such that all necessary setting are in place for both HTTP and HTTPS listeners when installed as you seem to imply that you manually added some of these entries ?

Does any additional error occur in the virtuoso.log log file at the time of the error. Note you can also enable additional tracing to the virtuoso.log file with the trace_on() functions and set “PLDebug = 1” and “CallStackOnException = 2” in the [Parameters] section of the virtuoso.ini file and restart Virtuoso, which will write any additional error messages to the client application layer.

Hi Hugh, thx for your reply.

I’m indeed using the OS version.

I configured the HTTPS listener only recently although I’ve had the server running for a while. So the faceted browser VAD was installed before enabling HTTPS. Should I uninstall and reinstall it?

I’ll have a look at the log file asap. It might take a few days though, here in France this will be a long week-end with July 14th (equivalent to your Jul. 4th ;)).


Hi Hugh,

I tried to go further on this issue.
I’ve uninstalled and reinstalled the faceted browser VAD but no change.
I’ve activated the log as you suggested: when I access /describe using https nothing shows in the virtuoso.log, but there is an http status 403 in the http.log file, and this is it: - - [27/Jul/2020:16:16:03 +0300] "GET /describe/?url= HTTP/1.1" 403 140 "" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0"

No other trace whereas there are quite a lot of other traces when accessed using http.

Note that conductor works fine with https.

Any ideas?


As a complement of my previous comment, something puzzles me: there are very little web services and “Hosted Domains and Virtual Directories” in https, as compared to http.


Hi, I guess I’ve had no further response to my last messages on this issue.
Could you please have a look?


In the screenshot you provide of the HTTP Listener on port 4443 Virtual Directories, I only see the /describe having been created, and if I do just that then I get the The requested active content cannot be displayed due to execution restriction you report.

In order to get around the error I also cloned the Faceted Browser (fct) Virtual Directories from the default HTTP Listener Virtual Domain, which the /describe service is dependant on ie


Then the /describe pages loaded successfully …

Dear Hugh,

Great news, that works! Thanks a lot for your help.

Just one thing: when fct is installed, all these WS and virtual domains are created automatically. Why aren’t they created the same way for https? (even though a valid is certificate is not configured yet). That would save a lot of trouble, no?

Basically, I use Virtuoso as a pure RDF store and SPARQL endpoint. I admit that this whole WS and virtual domains configuration is a mysterious black box for me, but I’m probably not the only one. So I’m wondering whether I should have figured this out by myself, or if I missed the proper documentation somewhere. What do you think?

Anyway, great thanks again!

This is already something on the development todo list to automatically add these vdir to additional Vhosts created via the Conductor and not just the defaults, as users should not have to add these manually …

Ok awesome!