ERR_CONNECTION_REFUSED

[rohanshad]

Able to transiently get the ePad interface to show up on localhost before getting a blank 'error connection refused'. I figured this was a port forwarding issue, but port 80 is open (Network Utility on Mac), and problem persisted when turning off the firewall. Currently using Mac OS 10.15.6

Docker status:

Any ideas?

[emelalkim]

Hi, thanks for your interest in ePad. Did you put localhost as host? Unfortunately, localhost doesn't work as for containers localhost is themselves. You need to put your ip, public hostname or shared hostname for mac Let us know if that works Thanks,

…

On Sat, Aug 8, 2020 at 8:14 PM Rohan Shad ***@***.***> wrote: Able to transiently get the ePad interface to show up on localhost before getting a blank 'error connection refused'. I figured this was a port forwarding issue, but port 80 is open (Network Utility on Mac), and problem persisted when turning off the firewall. Currently using Mac OS 10.15.6 Docker status: [image: Screen Shot 2020-08-08 at 8 10 23 PM] <https://user-images.githubusercontent.com/12033026/89724072-346aa880-d9b3-11ea-8193-06aa058d90f4.png> Any ideas? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#163>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXQXTU2B5G6Z3AG52S37JTR7YIBHANCNFSM4PY67NJQ> .

[rohanshad]

I used the Mac shared hostname for the host field in the .yml file. That looked something like this: Computer_Name.local Rohan On Aug 10, 2020, at 4:54 PM, Emel ALKIM <notifications@github.com> wrote: Hi, thanks for your interest in ePad. Did you put localhost as host? Unfortunately, localhost doesn't work as for containers localhost is themselves. You need to put your ip, public hostname or shared hostname for mac Let us know if that works Thanks,

On Sat, Aug 8, 2020 at 8:14 PM Rohan Shad ***@***.***> wrote: Able to transiently get the ePad interface to show up on localhost before getting a blank 'error connection refused'. I figured this was a port forwarding issue, but port 80 is open (Network Utility on Mac), and problem persisted when turning off the firewall. Currently using Mac OS 10.15.6 Docker status: [image: Screen Shot 2020-08-08 at 8 10 23 PM] <https://user-images.githubusercontent.com/12033026/89724072-346aa880-d9b3-11ea-8193-06aa058d90f4.png> Any ideas? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#163>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXQXTU2B5G6Z3AG52S37JTR7YIBHANCNFSM4PY67NJQ> .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#163 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC3ZYAQ5TBBODO2RBP3GNLLSACCDFANCNFSM4PY67NJQ>.

[emelalkim]

Hi, do you see the url change back to localhost? or do you see 401 with network calls? does the authentication screen show up? can you send a screenshot? Thanks

…

On Mon, Aug 10, 2020, 4:58 PM Rohan Shad ***@***.***> wrote: I used the Mac shared hostname for the host field in the .yml file. That looked something like this: Computer_Name.local Rohan On Aug 10, 2020, at 4:54 PM, Emel ALKIM ***@***.***> wrote: Hi, thanks for your interest in ePad. Did you put localhost as host? Unfortunately, localhost doesn't work as for containers localhost is themselves. You need to put your ip, public hostname or shared hostname for mac Let us know if that works Thanks, On Sat, Aug 8, 2020 at 8:14 PM Rohan Shad ***@***.***> wrote: > Able to transiently get the ePad interface to show up on localhost before > getting a blank 'error connection refused'. I figured this was a port > forwarding issue, but port 80 is open (Network Utility on Mac), and problem > persisted when turning off the firewall. Currently using Mac OS 10.15.6 > > Docker status: > [image: Screen Shot 2020-08-08 at 8 10 23 PM] > < https://user-images.githubusercontent.com/12033026/89724072-346aa880-d9b3-11ea-8193-06aa058d90f4.png > > > Any ideas? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#163>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAXQXTU2B5G6Z3AG52S37JTR7YIBHANCNFSM4PY67NJQ > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < #163 (comment)>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AC3ZYAQ5TBBODO2RBP3GNLLSACCDFANCNFSM4PY67NJQ >. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#163 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXQXTVDK4HGPCSQNEIDKNTSACCR5ANCNFSM4PY67NJQ> .