Redirect port 80 to 8080 and make it work on local machine












49















I redirected traffic for port 80 to 8080 on my machine with



sudo iptables -A PREROUTING -t nat -p tcp --dport 80 -j REDIRECT --to-ports 8080


It works fine for all the world except my own machine. I am a developer and I need to redirect port 80 to 8080 for myself.



My IP is 192.168.0.111



My web server runs on port 8080



I wish to open website from http://192.168.0.111/ instead of http://192.168.0.111:8080/ from same machine where server runs.






iptables port-forwarding







share|improve this question

























  • Excuse me for the abberation, but what is the purpose of forwarding port 80 to 8080?

    – ma11hew28
    Nov 10 '14 at 5:10






  • 1





    @mattdipasquale, normal users can't access port 80 so you couldn't run a web service like python flask as a normal user.

    – Christian
    Mar 29 '16 at 10:14











  • Why don't you just bind the web server to port 80?

    – David Foerster
    May 23 '16 at 13:01






  • 3





    i'd guess its because non-root user cannot bind to ports 80/443 and he doesnt want to run his web service as root..

    – Pavel K.
    Oct 11 '16 at 10:35
















49















I redirected traffic for port 80 to 8080 on my machine with



sudo iptables -A PREROUTING -t nat -p tcp --dport 80 -j REDIRECT --to-ports 8080


It works fine for all the world except my own machine. I am a developer and I need to redirect port 80 to 8080 for myself.



My IP is 192.168.0.111



My web server runs on port 8080



I wish to open website from http://192.168.0.111/ instead of http://192.168.0.111:8080/ from same machine where server runs.






iptables port-forwarding







share|improve this question

























  • Excuse me for the abberation, but what is the purpose of forwarding port 80 to 8080?

    – ma11hew28
    Nov 10 '14 at 5:10






  • 1





    @mattdipasquale, normal users can't access port 80 so you couldn't run a web service like python flask as a normal user.

    – Christian
    Mar 29 '16 at 10:14











  • Why don't you just bind the web server to port 80?

    – David Foerster
    May 23 '16 at 13:01






  • 3





    i'd guess its because non-root user cannot bind to ports 80/443 and he doesnt want to run his web service as root..

    – Pavel K.
    Oct 11 '16 at 10:35














49












49








49


28






I redirected traffic for port 80 to 8080 on my machine with



sudo iptables -A PREROUTING -t nat -p tcp --dport 80 -j REDIRECT --to-ports 8080


It works fine for all the world except my own machine. I am a developer and I need to redirect port 80 to 8080 for myself.



My IP is 192.168.0.111



My web server runs on port 8080



I wish to open website from http://192.168.0.111/ instead of http://192.168.0.111:8080/ from same machine where server runs.






iptables port-forwarding







share|improve this question
















I redirected traffic for port 80 to 8080 on my machine with



sudo iptables -A PREROUTING -t nat -p tcp --dport 80 -j REDIRECT --to-ports 8080


It works fine for all the world except my own machine. I am a developer and I need to redirect port 80 to 8080 for myself.



My IP is 192.168.0.111



My web server runs on port 8080



I wish to open website from http://192.168.0.111/ instead of http://192.168.0.111:8080/ from same machine where server runs.






iptables port-forwarding




iptables port-forwarding






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 29 '18 at 9:44









heemayl

66.9k8141214




66.9k8141214










asked Apr 7 '14 at 23:40









MaxMax

448157




448157













  • Excuse me for the abberation, but what is the purpose of forwarding port 80 to 8080?

    – ma11hew28
    Nov 10 '14 at 5:10






  • 1





    @mattdipasquale, normal users can't access port 80 so you couldn't run a web service like python flask as a normal user.

    – Christian
    Mar 29 '16 at 10:14











  • Why don't you just bind the web server to port 80?

    – David Foerster
    May 23 '16 at 13:01






  • 3





    i'd guess its because non-root user cannot bind to ports 80/443 and he doesnt want to run his web service as root..

    – Pavel K.
    Oct 11 '16 at 10:35



















  • Excuse me for the abberation, but what is the purpose of forwarding port 80 to 8080?

    – ma11hew28
    Nov 10 '14 at 5:10






  • 1





    @mattdipasquale, normal users can't access port 80 so you couldn't run a web service like python flask as a normal user.

    – Christian
    Mar 29 '16 at 10:14











  • Why don't you just bind the web server to port 80?

    – David Foerster
    May 23 '16 at 13:01






  • 3





    i'd guess its because non-root user cannot bind to ports 80/443 and he doesnt want to run his web service as root..

    – Pavel K.
    Oct 11 '16 at 10:35

















Excuse me for the abberation, but what is the purpose of forwarding port 80 to 8080?

– ma11hew28
Nov 10 '14 at 5:10





Excuse me for the abberation, but what is the purpose of forwarding port 80 to 8080?

– ma11hew28
Nov 10 '14 at 5:10




1




1





@mattdipasquale, normal users can't access port 80 so you couldn't run a web service like python flask as a normal user.

– Christian
Mar 29 '16 at 10:14





@mattdipasquale, normal users can't access port 80 so you couldn't run a web service like python flask as a normal user.

– Christian
Mar 29 '16 at 10:14













Why don't you just bind the web server to port 80?

– David Foerster
May 23 '16 at 13:01





Why don't you just bind the web server to port 80?

– David Foerster
May 23 '16 at 13:01




3




3





i'd guess its because non-root user cannot bind to ports 80/443 and he doesnt want to run his web service as root..

– Pavel K.
Oct 11 '16 at 10:35





i'd guess its because non-root user cannot bind to ports 80/443 and he doesnt want to run his web service as root..

– Pavel K.
Oct 11 '16 at 10:35










3 Answers
3






active

oldest

votes


















69














You need to use the OUTPUT chain as the packets meant for the loopback interface do not pass via the PREROUTING chain. The following should work; run as root:



iptables -t nat -A OUTPUT -o lo -p tcp --dport 80 -j REDIRECT --to-port 8080





share|improve this answer





















  • 1





    Does port 80 required to be gloabally accesible? I tried your solution, my port number 8080 is accessible but 80 is not hence it did not worked. @heemayl

    – alper
    Jul 28 '17 at 23:39








  • 2





    This did not work, not sure why this is voted up

    – Diyoda_
    Mar 5 '18 at 22:11











  • @Diyoda_ Please define did not work.

    – heemayl
    Mar 29 '18 at 9:44











  • @Alper I think you didn't read the OPs question.

    – styl3r
    Apr 23 '18 at 22:19











  • I can confirm that this doesn't work on ubuntu 18.04

    – Ahmed Hamdy
    Jun 24 '18 at 11:23



















3














Instead of the iptables, You could try:

sudo ssh -gL 80:127.0.0.1:8080 localhost






share|improve this answer



















  • 2





    That is an option but it is not exactly what I want because I already have web server on port 80. I will prefer to do it with iptables and keep web server on port 80 running. I guess I just have to apply rule to different step instead of PREROUTING

    – Max
    Apr 8 '14 at 10:45











  • Yes - this will cause a port conflict if you have something listening that you are port forwarding to as Max suggested. The above answer is the more general case.

    – cgseller
    Nov 15 '16 at 20:24



















0














Simple just use iptables allowing both port 80 and 8080 then redirect 80 to 8080 make sure you are assigning to the correct nic.. in example I use eth0 



iptables -A INPUT -i eth0 -p tcp --dport 80 -j ACCEPT

iptables -A INPUT -i eth0 -p tcp --dport 8080 -j ACCEPT

iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080





share|improve this answer










New contributor




tmac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f444729%2fredirect-port-80-to-8080-and-make-it-work-on-local-machine%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    69














    You need to use the OUTPUT chain as the packets meant for the loopback interface do not pass via the PREROUTING chain. The following should work; run as root:



    iptables -t nat -A OUTPUT -o lo -p tcp --dport 80 -j REDIRECT --to-port 8080





    share|improve this answer





















    • 1





      Does port 80 required to be gloabally accesible? I tried your solution, my port number 8080 is accessible but 80 is not hence it did not worked. @heemayl

      – alper
      Jul 28 '17 at 23:39








    • 2





      This did not work, not sure why this is voted up

      – Diyoda_
      Mar 5 '18 at 22:11











    • @Diyoda_ Please define did not work.

      – heemayl
      Mar 29 '18 at 9:44











    • @Alper I think you didn't read the OPs question.

      – styl3r
      Apr 23 '18 at 22:19











    • I can confirm that this doesn't work on ubuntu 18.04

      – Ahmed Hamdy
      Jun 24 '18 at 11:23
















    69














    You need to use the OUTPUT chain as the packets meant for the loopback interface do not pass via the PREROUTING chain. The following should work; run as root:



    iptables -t nat -A OUTPUT -o lo -p tcp --dport 80 -j REDIRECT --to-port 8080





    share|improve this answer





















    • 1





      Does port 80 required to be gloabally accesible? I tried your solution, my port number 8080 is accessible but 80 is not hence it did not worked. @heemayl

      – alper
      Jul 28 '17 at 23:39








    • 2





      This did not work, not sure why this is voted up

      – Diyoda_
      Mar 5 '18 at 22:11











    • @Diyoda_ Please define did not work.

      – heemayl
      Mar 29 '18 at 9:44











    • @Alper I think you didn't read the OPs question.

      – styl3r
      Apr 23 '18 at 22:19











    • I can confirm that this doesn't work on ubuntu 18.04

      – Ahmed Hamdy
      Jun 24 '18 at 11:23














    69












    69








    69







    You need to use the OUTPUT chain as the packets meant for the loopback interface do not pass via the PREROUTING chain. The following should work; run as root:



    iptables -t nat -A OUTPUT -o lo -p tcp --dport 80 -j REDIRECT --to-port 8080





    share|improve this answer















    You need to use the OUTPUT chain as the packets meant for the loopback interface do not pass via the PREROUTING chain. The following should work; run as root:



    iptables -t nat -A OUTPUT -o lo -p tcp --dport 80 -j REDIRECT --to-port 8080






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Jun 24 '18 at 11:50

























    answered Jan 30 '15 at 5:15









    heemaylheemayl

    66.9k8141214




    66.9k8141214








    • 1





      Does port 80 required to be gloabally accesible? I tried your solution, my port number 8080 is accessible but 80 is not hence it did not worked. @heemayl

      – alper
      Jul 28 '17 at 23:39








    • 2





      This did not work, not sure why this is voted up

      – Diyoda_
      Mar 5 '18 at 22:11











    • @Diyoda_ Please define did not work.

      – heemayl
      Mar 29 '18 at 9:44











    • @Alper I think you didn't read the OPs question.

      – styl3r
      Apr 23 '18 at 22:19











    • I can confirm that this doesn't work on ubuntu 18.04

      – Ahmed Hamdy
      Jun 24 '18 at 11:23














    • 1





      Does port 80 required to be gloabally accesible? I tried your solution, my port number 8080 is accessible but 80 is not hence it did not worked. @heemayl

      – alper
      Jul 28 '17 at 23:39








    • 2





      This did not work, not sure why this is voted up

      – Diyoda_
      Mar 5 '18 at 22:11











    • @Diyoda_ Please define did not work.

      – heemayl
      Mar 29 '18 at 9:44











    • @Alper I think you didn't read the OPs question.

      – styl3r
      Apr 23 '18 at 22:19











    • I can confirm that this doesn't work on ubuntu 18.04

      – Ahmed Hamdy
      Jun 24 '18 at 11:23








    1




    1





    Does port 80 required to be gloabally accesible? I tried your solution, my port number 8080 is accessible but 80 is not hence it did not worked. @heemayl

    – alper
    Jul 28 '17 at 23:39







    Does port 80 required to be gloabally accesible? I tried your solution, my port number 8080 is accessible but 80 is not hence it did not worked. @heemayl

    – alper
    Jul 28 '17 at 23:39






    2




    2





    This did not work, not sure why this is voted up

    – Diyoda_
    Mar 5 '18 at 22:11





    This did not work, not sure why this is voted up

    – Diyoda_
    Mar 5 '18 at 22:11













    @Diyoda_ Please define did not work.

    – heemayl
    Mar 29 '18 at 9:44





    @Diyoda_ Please define did not work.

    – heemayl
    Mar 29 '18 at 9:44













    @Alper I think you didn't read the OPs question.

    – styl3r
    Apr 23 '18 at 22:19





    @Alper I think you didn't read the OPs question.

    – styl3r
    Apr 23 '18 at 22:19













    I can confirm that this doesn't work on ubuntu 18.04

    – Ahmed Hamdy
    Jun 24 '18 at 11:23





    I can confirm that this doesn't work on ubuntu 18.04

    – Ahmed Hamdy
    Jun 24 '18 at 11:23













    3














    Instead of the iptables, You could try:

    sudo ssh -gL 80:127.0.0.1:8080 localhost






    share|improve this answer



















    • 2





      That is an option but it is not exactly what I want because I already have web server on port 80. I will prefer to do it with iptables and keep web server on port 80 running. I guess I just have to apply rule to different step instead of PREROUTING

      – Max
      Apr 8 '14 at 10:45











    • Yes - this will cause a port conflict if you have something listening that you are port forwarding to as Max suggested. The above answer is the more general case.

      – cgseller
      Nov 15 '16 at 20:24
















    3














    Instead of the iptables, You could try:

    sudo ssh -gL 80:127.0.0.1:8080 localhost






    share|improve this answer



















    • 2





      That is an option but it is not exactly what I want because I already have web server on port 80. I will prefer to do it with iptables and keep web server on port 80 running. I guess I just have to apply rule to different step instead of PREROUTING

      – Max
      Apr 8 '14 at 10:45











    • Yes - this will cause a port conflict if you have something listening that you are port forwarding to as Max suggested. The above answer is the more general case.

      – cgseller
      Nov 15 '16 at 20:24














    3












    3








    3







    Instead of the iptables, You could try:

    sudo ssh -gL 80:127.0.0.1:8080 localhost






    share|improve this answer













    Instead of the iptables, You could try:

    sudo ssh -gL 80:127.0.0.1:8080 localhost







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Apr 8 '14 at 0:06









    GregorGregor

    28416




    28416








    • 2





      That is an option but it is not exactly what I want because I already have web server on port 80. I will prefer to do it with iptables and keep web server on port 80 running. I guess I just have to apply rule to different step instead of PREROUTING

      – Max
      Apr 8 '14 at 10:45











    • Yes - this will cause a port conflict if you have something listening that you are port forwarding to as Max suggested. The above answer is the more general case.

      – cgseller
      Nov 15 '16 at 20:24














    • 2





      That is an option but it is not exactly what I want because I already have web server on port 80. I will prefer to do it with iptables and keep web server on port 80 running. I guess I just have to apply rule to different step instead of PREROUTING

      – Max
      Apr 8 '14 at 10:45











    • Yes - this will cause a port conflict if you have something listening that you are port forwarding to as Max suggested. The above answer is the more general case.

      – cgseller
      Nov 15 '16 at 20:24








    2




    2





    That is an option but it is not exactly what I want because I already have web server on port 80. I will prefer to do it with iptables and keep web server on port 80 running. I guess I just have to apply rule to different step instead of PREROUTING

    – Max
    Apr 8 '14 at 10:45





    That is an option but it is not exactly what I want because I already have web server on port 80. I will prefer to do it with iptables and keep web server on port 80 running. I guess I just have to apply rule to different step instead of PREROUTING

    – Max
    Apr 8 '14 at 10:45













    Yes - this will cause a port conflict if you have something listening that you are port forwarding to as Max suggested. The above answer is the more general case.

    – cgseller
    Nov 15 '16 at 20:24





    Yes - this will cause a port conflict if you have something listening that you are port forwarding to as Max suggested. The above answer is the more general case.

    – cgseller
    Nov 15 '16 at 20:24











    0














    Simple just use iptables allowing both port 80 and 8080 then redirect 80 to 8080 make sure you are assigning to the correct nic.. in example I use eth0 



    iptables -A INPUT -i eth0 -p tcp --dport 80 -j ACCEPT
    
iptables -A INPUT -i eth0 -p tcp --dport 8080 -j ACCEPT
    
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080





    share|improve this answer










    New contributor




    tmac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      0














      Simple just use iptables allowing both port 80 and 8080 then redirect 80 to 8080 make sure you are assigning to the correct nic.. in example I use eth0 



      iptables -A INPUT -i eth0 -p tcp --dport 80 -j ACCEPT
      
iptables -A INPUT -i eth0 -p tcp --dport 8080 -j ACCEPT
      
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080





      share|improve this answer










      New contributor




      tmac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        0












        0








        0







        Simple just use iptables allowing both port 80 and 8080 then redirect 80 to 8080 make sure you are assigning to the correct nic.. in example I use eth0 



        iptables -A INPUT -i eth0 -p tcp --dport 80 -j ACCEPT
        
iptables -A INPUT -i eth0 -p tcp --dport 8080 -j ACCEPT
        
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080





        share|improve this answer










        New contributor




        tmac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        Simple just use iptables allowing both port 80 and 8080 then redirect 80 to 8080 make sure you are assigning to the correct nic.. in example I use eth0 



        iptables -A INPUT -i eth0 -p tcp --dport 80 -j ACCEPT
        
iptables -A INPUT -i eth0 -p tcp --dport 8080 -j ACCEPT
        
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080






        share|improve this answer










        New contributor




        tmac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer








        edited 1 hour ago









        Kevin Bowen

        14.5k155970




        14.5k155970






        New contributor




        tmac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 2 hours ago









        tmactmac

        1




        1




        New contributor




        tmac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        tmac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        tmac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid …



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f444729%2fredirect-port-80-to-8080-and-make-it-work-on-local-machine%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            -

            Popular posts from this blog

            數位音樂下載

            Image
            數位音樂下載 為非以「實體」方式來販賣音樂的相關產品，而使用數位格式如mp3、AAC等文件格式來進行銷售販賣的一种音乐产业形式。著名的數位音樂下載服務商有iTunes Store、RecoChoku、Google Play音乐和微软Zune等。数字音乐下载在二十一世纪初一度风靡全球， [1] [2] 使得传统唱片产业走向衰落，但其自身也在2010年代流媒体音乐服务如Apple Music、Spotify等的挤压下迅速失去市场份额。 [3] [4] 数字音乐下载有便于携带、传播迅速、制作简单成本低等优点，与流媒体音乐相比也能更好保障音乐人权益； [5] 但它同时很可能带来侵犯版权和滥用的情形， [6] 也给音乐产业带来了诸多不利影响。数字音乐下载为音乐人和乐迷提供了更加便捷直接的交流渠道，也一定程度上推动了网络音乐人的出现和独立音乐的迅速发展。 [7] 目录 1 历史 1.1 技术积淀（1987-2000） 1.2 出现与兴起（2000-2004） 1.3 唱片市场的颠覆者（2004-2007） 1.4 巅峰和衰落（2005-2013） 1.5 摇摇欲坠的现状与不可预知的明天（2014至今） 2 主要文件格式 2.1 PCM编码格式 2.1.1 WAV 2.1.2 APE 2.1.3 FLAC 2.2 苹果推出的无损文件格式 2.2.1 AIFF 2.2.2 ALAC 2.3 有损压缩格式 2.3.1 MP3 2.3.2 AAC 3 主要市场 3.1 iTunes Store 3.2 Google Play音乐商店 3.3 亚马逊音乐商店 3.4 部分其他音乐商店 4 影响与评价 4.1 对音乐产业的影响 4.2 对科技行业的影响 4.3 正面评价 4.4 负面评价 4.4.1 侵权问题 4.4.2 经营模式不明晰 4.4.3 不适应移动时代 4.5 文化现象 5 延伸阅读 6 参考资料 历史 苹果iTunes+iPod的软硬件搭配让数字音...
            Read more

            When can things happen in Etherscan, such as the picture below?

            Image
            2 I don't know why balance of the address is 0. when can this situation? etherscan balances share | improve this question asked yesterday Ru Hi Ru Hi 11 1 New contributor Ru Hi is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment  |  ...
            Read more

            格利澤436b

            Image
            格利泽436b 太陽系外行星 太陽系外行星列表 艺术家笔下的格利泽436b 母恆星 母恆星 Gliese 436 星座 獅子座 赤經 ( α ) 11 h  42 m  11.0941 s [1] 赤緯 ( δ ) +26° 42′ 23.652″ [1] 距離 33.4 ly (10.2 pc) 光譜類型 M2.5 V [1] 軌道參數 半长轴 ( a ) 0.0291±0.0004 [2] AU 軌道離心率 ( e ) 0.150±0.012 [2] 公轉週期 ( P ) 2.643904±0.000005 [3] d (0.00723849 y) 軌道傾角 ( i ) 85.8 +0.21 −0.25 [3] ° 角距 ( θ ) 2.794 mas 近星點時間 ( T 0 ) 2,451,551.716 ±0.01 JD 半振幅 ( K ) 18.68±0.8 m/s 物理性质 质量 ( m ) 22.2±1.0 [2] M ⊕ 半徑 ( r ) 4.327±0.183 [2] [4] R ⊕ 密度 ( ρ ) 1.51 g cm -3 表面重力 ( g ) 1.18 g 溫度 ( T ) 712±36 [2] K 發現 發現時間 2004 發現者 巴特勒、沃格特、 馬西 et al. 發現方法 徑向速度、凌日法 發現地點 美國加利福尼亞州 發表論文 出版 其他名稱 Ross 905 b, GJ 436 b, [5] LTT 13213 b, GCTP 2704.10 b, LHS 310, AC+27:28217 b, Vyssotsky 616 b, HIP 57087 b, GEN# +9.80120068 b, LP 319-75 b, G 121-7 b, LSPM J1142+2642 b, 1RXS J114211.9+264328 b, ASCC 683818 b, G 147-68 b, UCAC2 41198281 b, BP...
            Read more