›
Welcome to the SRP Forum! Please refer to the SRP Forum FAQ post if you have any questions regarding how the forum works.

Abyss web server X1: removing port number from URL

SMirzaSMirza
in SRP HTTP Framework
Greetings!

We have our OpenInsight in Microsoft Azure Windows Virtual Machine (VM) and we are using Abyss web server X1 for hosting a website. 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. Although, the default port number or the other port numbers work when I try to access the website locally in the Azure Windows VM.

To access the website remotely, I had to create an Inbound Rule in VM's Windows Firewall for port 8080. 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.

In our OpenInsight, the current SRP_HTTP_FRAMEWORK_SETUP record looks like:

http://xxxx.yyyyy.com
/api
C:\folder_name\srp_http_debug
1
REALM_NAME
Entry_Point
1

We want to remove the port number (8080) from the website URL while accessing remotely.

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.

Please let me know if you want me to clarify anything or if you need any additional information. I would appreciate any suggestion.

Thanks,

Sharoz

Comments

  • DonBakkeDonBakke
    Greetings to you as well. If I recall correctly, won't you be applying an SSL cert to this site? If that is the case, may I ask why you you are looking to support http instead of just https? I'm not looking to avoid answering your question but I am wondering if your question needs to be answered. Let me know and we'll try to move forward as necessary.
  • SMirzaSMirza
    Mostly for test run. We applied for a renewal of our current SSL certificate and still waiting for it.
  • DonBakkeDonBakke
    I see. Okay, well I'll share my thoughts on this but I am willing to be corrected by others on my team or in this forum. Browsers will always use port 80 as the default for http traffic and port 443 for https traffic. If you want or need to use an alternative port for listening to incoming http traffic, the URL must specify the port. I do not believe you can work around this.

    Therefore, I would try to resolve why you cannot use port 80 on your Azure server. If you configured this specifically to be a VM web server then this should not be a problem.
  • SMirzaSMirza
    I attached the Abyss server console and the firewall configuration screenshots. Do they look good to you? Like I said before, port 80 works locally in the VM but not remotely.
  • DonBakkeDonBakke
    The Abyss configuration looks perfectly good to me. This is corroborated by your successful internal (local) tests. I am certain the problem lies in the way your web server is routing traffic coming in over port 80. Regarding the firewall, this is a little bit outside of my experience. I believe you have this configured to allow all ports for remote traffic and you have it configured to only support port 80 for internal traffic. I would have assumed this would work, but apparently it isn't. I'm going to see if someone else on my team can chime in before making further suggestions.
  • SMirzaSMirza
    We got our SSL certificate today. I believe I installed it correctly and the default secure host is running on port 443. Now the internal tests are not successful. I tried with both https://127.0.0.1/api and https://127.0.0.1:443/api, and none of these worked.
  • CorbyNagelCorbyNagel
    It has been a while since I have used Azure but if it is anything like Amazon Web Services there will be a firewall setting in your hosting control panel. This is an external firewall before your Windows Server firewall that blocks traffic before it hits the Windows firewall. You will need to add in rules for port 80 and 443 at that level first and then make sure port 80 and 443 is open at the OS level.

    Can you also tell me how you got to the window found in the Firewall.jpg image? It looks familiar but I can't seem to locate it. Also what OS are you running this on?
  • SMirzaSMirza
    Mr. Nagel,

    You are spot on. 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. Port 80 is working now, that means I am not using any port number with my website URL when I use HTTP protocol. 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.

    To view the properties for an inbound rule in the windows firewall settings this is what I did.

    1. Clicked windows key
    2. typed 'firewall'
    3. selected 'Windows firewall with advanced security' from the search items
    4. clicked 'Inbound rules'
    5. selected an inbound rule from the inbound rule list and went to it's properties.
    6. finally, selected 'Protocols and ports' tab.

    I am using Windows Server 2012 R2

    Thank you very much for your help. I really appreciate it.

    - Sharoz
Sign In or Register to comment.