Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not reaching app #324

Closed
chrise86 opened this issue Nov 9, 2022 · 2 comments
Closed

Not reaching app #324

chrise86 opened this issue Nov 9, 2022 · 2 comments

Comments

@chrise86
Copy link

chrise86 commented Nov 9, 2022

I appreciate this is probably not an issue with puma-dev but I have no idea how to go about debugging this. I'm using an Intel mac mini, was on 12.x and now on 13, but neither worked.

Everything seems to install fine, no errors in the logs that I can see, but hitting myapp.test or (myapp.puma, or anything else I've tried) immediately returns the browser's "not found message".

I have noticed it's immediately redirecting to https:// too, but have no idea why. This also happens no matter what the tld. Booting it manually and using port 9280 does work, though, as does accessing the Rails app normally via 3000 / etc.

Using ping myapp.test or dscacheutil -q host -a name myapp.test returns exactly what you'd expect, i.e. 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.040 ms

scutil --dns also suggests that the resolver is being used as it contains (when using .puma):

resolver #8
  domain   : puma
  nameserver[0] : 127.0.0.1
  port     : 9253
  flags    : Request A records, Request AAAA records
  reach    : 0x00030002 (Reachable,Local Address,Directly Reachable Address)

I've also tried adding search puma to the resolver, which correctly returns:

resolver #8
  domain   : puma
  search domain[0] : puma
  nameserver[0] : 127.0.0.1
  port     : 9253
  flags    : Request A records, Request AAAA records
  reach    : 0x00030002 (Reachable,Local Address,Directly Reachable Address)

Still nothing works.

@chrise86
Copy link
Author

chrise86 commented Nov 9, 2022

Turns out it must have been something to do with Pow (although I didn't think I'd ever used it on this machine) as following the steps here seems to have solved accessing the app via http://, but now https:// yields Secure Connection Failed

@chrise86
Copy link
Author

chrise86 commented Nov 9, 2022

Resolved SSL issue using #84

@chrise86 chrise86 closed this as completed Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant