# HTTPS access for OpenPDC Console and Historian (6051 and 6052)

**URL:** <http://discussions.gridprotectionalliance.org/t/https-access-for-openpdc-console-and-historian-6051-and-6052/1359>\
**Category:** openPDC\
**Created:** [January 14, 2025, 4:08am UTC](http://discussions.gridprotectionalliance.org/t/https-access-for-openpdc-console-and-historian-6051-and-6052/1359 "2025-01-14T04:08:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nicolas\_Pierim](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/nicolas_pierim/32/982_2.png) [@Nicolas\_Pierim](http://discussions.gridprotectionalliance.org/u/Nicolas_Pierim)\
**Post date:** [January 14, 2025, 4:08am UTC](http://discussions.gridprotectionalliance.org/t/https-access-for-openpdc-console-and-historian-6051-and-6052/1359/1 "2025-01-14T04:08:24Z")

</div>

I searched the forum for some questions about HTTPS access and found some references to OpenHistorian.

I would like to know if it is possible to configure and access the following URLs with HTTPS:

[http://localhost:8280/](http://localhost:8280/) and the Statistics metadata web service, e.g.:

[http://localhost:6051/historian/metadata/read/xml](http://localhost:6051/historian/metadata/read/xml)

Statistics data web service, e.g.:

[http://localhost:6052/historian/timeseriesdata/read/current/32/json](http://localhost:6052/historian/timeseriesdata/read/current/32/json)

If it is possible, could you describe the main steps to configure it to run in a Windows Server environment?

---

<div class="post-metadata">

**Author:** ![StephenCWills](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/stephencwills/32/20_2.png) [@StephenCWills](http://discussions.gridprotectionalliance.org/u/StephenCWills)\
**Post date:** [January 14, 2025, 4:10pm UTC](http://discussions.gridprotectionalliance.org/t/https-access-for-openpdc-console-and-historian-6051-and-6052/1359/2 "2025-01-14T16:10:11Z")

</div>

It looks to me like the answer is no. I’d say your best bet is to lock down access to the http port using a firewall and then set up a proxy for each endpoint.