# Example Web Dev Python endpoint that uses https **URL:** \ **Category:** Ignition\ **Tags:** webdev\ **Created:** [October 15, 2024, 9:47pm UTC](https://forum.inductiveautomation.com/t/example-web-dev-python-endpoint-that-uses-https/97281 "2024-10-15T21:47:06Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Isaiah\_Clemons](https://avatars.discourse-cdn.com/v4/letter/i/dc4da7/32.png) [@Isaiah\_Clemons](https://forum.inductiveautomation.com/u/Isaiah_Clemons)\ **Post date:** [October 15, 2024, 9:47pm UTC](https://forum.inductiveautomation.com/t/example-web-dev-python-endpoint-that-uses-https/97281/1 "2024-10-15T21:47:06Z")
Hello, I am trying to create an API endpoint using the web dev module in Ignition Designer, and i would like to use https instead of the non-encrypted http, some more information about this would be appreciated. I have looked through [this](https://www.docs.inductiveautomation.com/docs/8.1/platform/gateway/config/web-server-settings/secure-communication-ssl-tls) documentation, I found the section on self signing but I was wondering what I do if I don't have a domain name that I can use? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [October 15, 2024, 10:07pm UTC](https://forum.inductiveautomation.com/t/example-web-dev-python-endpoint-that-uses-https/97281/2 "2024-10-15T22:07:52Z")
You don't need a domain name to **self** -sign a certificate. All \[1\] public certificate authorities (CA)s require a domain name to generate a **valid** certificate, but all validity means is that your OS/browser will _by default_ trust your certificates. On pretty much all platforms, and certainly on everywhere you can run Ignition, you can create your own "certificate authority", trust that authority from your HTTP client(s), and then tell Ignition to use that CA for its own web communication. You will need to enable SSL for the gateway as a whole **and** for specific Webdev endpoints: > **[Web Dev | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/web-dev#require-https)** > > The Web Dev module enables you to directly program against the web server inside the Ignition Gateway. Webpages can be built by hand using a combination of Python programming and static web resources such as images, CSS files, JavaScript files, and... * * * 1. probably ---
**Author:** ![Isaiah\_Clemons](https://avatars.discourse-cdn.com/v4/letter/i/dc4da7/32.png) [@Isaiah\_Clemons](https://forum.inductiveautomation.com/u/Isaiah_Clemons)\ **Post date:** [October 16, 2024, 7:30pm UTC](https://forum.inductiveautomation.com/t/example-web-dev-python-endpoint-that-uses-https/97281/3 "2024-10-16T19:30:30Z")
Thank You! ---
**Author:** ![Isaiah\_Clemons](https://avatars.discourse-cdn.com/v4/letter/i/dc4da7/32.png) [@Isaiah\_Clemons](https://forum.inductiveautomation.com/u/Isaiah_Clemons)\ **Post date:** [October 16, 2024, 11:32pm UTC](https://forum.inductiveautomation.com/t/example-web-dev-python-endpoint-that-uses-https/97281/4 "2024-10-16T23:32:37Z")
Yesterday I had this working with the self signed certificate on my local network at the office between machines in order to do https and now that I am at the site on a different network and gateway, I have regenerated the self-signed certificate and enabled TLS and https on the endpoints in the new project on the gateway at site, but for some reason now when I try to send a request to the endpoint with https on port 8043 it simply times out. The endpoint still works on http if I disable https: in the designer. Any thoughts on this? Are there more steps that I should take to allow for https on the network on site? ---
**Author:** ![Isaiah\_Clemons](https://avatars.discourse-cdn.com/v4/letter/i/dc4da7/32.png) [@Isaiah\_Clemons](https://forum.inductiveautomation.com/u/Isaiah_Clemons)\ **Post date:** [October 17, 2024, 3:22pm UTC](https://forum.inductiveautomation.com/t/example-web-dev-python-endpoint-that-uses-https/97281/5 "2024-10-17T15:22:02Z")
Never mind I discovered the problem was that I needed to create a new rule in the firewall on site to allow for traffic through port 8043