finally, selected 'Protocols and ports' tab. selected an inbound rule from the inbound rule list and went to it's properties.Ħ. selected 'Windows firewall with advanced security' from the search itemsĥ. ![]() To view the properties for an inbound rule in the windows firewall settings this is what I did.ģ. I am still having problem when I use HTTPS protocol and I think I have to double check the configuration and SSL certificate set up in the Abyss Web Server for this because the internal tests are not successful for HTTPS. Port 80 is working now, that means I am not using any port number with my website URL when I use HTTP protocol. Yes, Azure does have an external firewall setting in the Azure VM portal and I had to create new inbound rules for both port 80 and 443 there as well as in Windows server's internal firewall settings. It supports SSL, compression, CGI/FastCGI, ISAPI, XSSI, URL rewriting,bandwidth throttling, anti-leeching, anti-hacking, and features a remote web management interface. It works on Linux too, and supports ASP.net using mono/fCGI under Linux, OSX and Windows. Please let me know if you want me to clarify anything or if you need any additional information. Abyss Web Server X1 is a free and compact Web server. 1 Answer Sorted by: 1 lighttpd is a good candidate, it is small, lightweight and supports CGI/fCGI. I am not sure if it would make any difference but I feel like I should mention that our website does not start with www. We want to remove the port number (8080) from the website URL while accessing remotely. In our OpenInsight, the current SRP_HTTP_FRAMEWORK_SETUP record looks like: Interestingly, when I run the default host on port 8080 everything works fine even if I do not specify the port number in the inbound rule properties whereas for the other port numbers we cannot have access to the website with specified port numbers in the inbound rule properties. To access the website remotely, I had to create an Inbound Rule in VM's Windows Firewall for port 8080. ![]() Now log into your web server for the first time using the username and password that was just created. lighttpd is a good candidate, it is small, lightweight and supports CGI/fCGI. Create a set of login credentials in the form of a username and password. Although, the default port number or the other port numbers work when I try to access the website locally in the Azure Windows VM. Click on Abyss Web Server icon on taskbar then right click and select Show Console in Abyss Server. I changed the port number for default host to 8080 from the default port number 80 in Abyss web server since only port 8080 works for the URL when I do a remote access, it does not work for the default (80) or other port numbers. We have our OpenInsight in Microsoft Azure Windows Virtual Machine (VM) and we are using Abyss web server X1 for hosting a website. ![]() We have our OpenInsight in Microsoft Azure Windows Virtual Machine (VM) and we are using Abyss web server X1 for hosting a website.
0 Comments
Leave a Reply. |