Apache2 external access issues [closed]

Multi tool use
Multi tool use












0















i am very much stuck on apache2 configuration. Reaching the web server internally works just fine, both with DNS and the servers local IP (with http://) but externally its a no go. I have added the servers public ip address to the A-record at my domain provider, port forwarded port 80 and 443 on my router and i have made sure apache2 listens to these ports.



I really dont understand what could be wrong, can any of you guys point me in the correct destination?










share|improve this question













closed as off-topic by vidarlo, Charles Green, Eric Carvalho, waltinator, user68186 Feb 4 at 15:03


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." – vidarlo, Charles Green, Eric Carvalho, waltinator, user68186

If this question can be reworded to fit the rules in the help center, please edit the question.

















  • From what you describe there's nothing wrong. If port forwarding is done correctly, what you describe should work. But you need to add more information, and I don't see how this is a Ubuntu problem either.

    – vidarlo
    Jan 21 at 19:37











  • Sometimes (especial when you change A-records) it takes some time (about 24 hours) to the whole DNS chain to be refreshed.

    – pa4080
    Jan 22 at 9:21
















0















i am very much stuck on apache2 configuration. Reaching the web server internally works just fine, both with DNS and the servers local IP (with http://) but externally its a no go. I have added the servers public ip address to the A-record at my domain provider, port forwarded port 80 and 443 on my router and i have made sure apache2 listens to these ports.



I really dont understand what could be wrong, can any of you guys point me in the correct destination?










share|improve this question













closed as off-topic by vidarlo, Charles Green, Eric Carvalho, waltinator, user68186 Feb 4 at 15:03


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." – vidarlo, Charles Green, Eric Carvalho, waltinator, user68186

If this question can be reworded to fit the rules in the help center, please edit the question.

















  • From what you describe there's nothing wrong. If port forwarding is done correctly, what you describe should work. But you need to add more information, and I don't see how this is a Ubuntu problem either.

    – vidarlo
    Jan 21 at 19:37











  • Sometimes (especial when you change A-records) it takes some time (about 24 hours) to the whole DNS chain to be refreshed.

    – pa4080
    Jan 22 at 9:21














0












0








0








i am very much stuck on apache2 configuration. Reaching the web server internally works just fine, both with DNS and the servers local IP (with http://) but externally its a no go. I have added the servers public ip address to the A-record at my domain provider, port forwarded port 80 and 443 on my router and i have made sure apache2 listens to these ports.



I really dont understand what could be wrong, can any of you guys point me in the correct destination?










share|improve this question














i am very much stuck on apache2 configuration. Reaching the web server internally works just fine, both with DNS and the servers local IP (with http://) but externally its a no go. I have added the servers public ip address to the A-record at my domain provider, port forwarded port 80 and 443 on my router and i have made sure apache2 listens to these ports.



I really dont understand what could be wrong, can any of you guys point me in the correct destination?







networking server apache2 dns






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 21 at 18:48









SiilverpantsSiilverpants

1




1




closed as off-topic by vidarlo, Charles Green, Eric Carvalho, waltinator, user68186 Feb 4 at 15:03


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." – vidarlo, Charles Green, Eric Carvalho, waltinator, user68186

If this question can be reworded to fit the rules in the help center, please edit the question.







closed as off-topic by vidarlo, Charles Green, Eric Carvalho, waltinator, user68186 Feb 4 at 15:03


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This is not about Ubuntu. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow." – vidarlo, Charles Green, Eric Carvalho, waltinator, user68186

If this question can be reworded to fit the rules in the help center, please edit the question.













  • From what you describe there's nothing wrong. If port forwarding is done correctly, what you describe should work. But you need to add more information, and I don't see how this is a Ubuntu problem either.

    – vidarlo
    Jan 21 at 19:37











  • Sometimes (especial when you change A-records) it takes some time (about 24 hours) to the whole DNS chain to be refreshed.

    – pa4080
    Jan 22 at 9:21



















  • From what you describe there's nothing wrong. If port forwarding is done correctly, what you describe should work. But you need to add more information, and I don't see how this is a Ubuntu problem either.

    – vidarlo
    Jan 21 at 19:37











  • Sometimes (especial when you change A-records) it takes some time (about 24 hours) to the whole DNS chain to be refreshed.

    – pa4080
    Jan 22 at 9:21

















From what you describe there's nothing wrong. If port forwarding is done correctly, what you describe should work. But you need to add more information, and I don't see how this is a Ubuntu problem either.

– vidarlo
Jan 21 at 19:37





From what you describe there's nothing wrong. If port forwarding is done correctly, what you describe should work. But you need to add more information, and I don't see how this is a Ubuntu problem either.

– vidarlo
Jan 21 at 19:37













Sometimes (especial when you change A-records) it takes some time (about 24 hours) to the whole DNS chain to be refreshed.

– pa4080
Jan 22 at 9:21





Sometimes (especial when you change A-records) it takes some time (about 24 hours) to the whole DNS chain to be refreshed.

– pa4080
Jan 22 at 9:21










0






active

oldest

votes

















0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes

VdSJHP6NdGpi r2imjMp,Osg1Vyd3RA,af 5Y,dtAVPSrh,ptC3Tflq8H SsnGy,vlaiPqG5A1
dHi1QbCzNrMDXb7

Popular posts from this blog

Running commands remotely through an RDP connection

Santo António de Lisboa

José Alencar