You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In test error, ranch reports that the address is already in use. If you can't see anything with lsof or e.g. telnet, it could perhaps be some race condition during the endpoint restart (e.g. the previous instance lingers on for awhile). However, I've never seen this happen so far. Is this failing during the test run, or is the app failing to start before the test even executes?
The prod error likely means that a self-signed certificate is used, which means that certification didn't start automatically. Do you see anything of interest in logs? Also, is mode perhaps configured to :manual?
Thanks for replying. The Production "issue" is solved by using the force_certify method as described in the README (at least in my case it's working so far). In Test, however, the culprit seems to be the function clean_restart() (it fails with the test running in isolation and with every other line commented out). Will check the method definition in your code whenever I get some time :)
Following the suggested steps in the README and Hexdocs fails both in development (test) and production using native client.
Development
In Dev, running the example test (as documented) returns "address already in use" although there is no process currently using in port 4002.
In
endpoint.ex
In the test file "as is"
This test fails with:
but lsof says there's nothing currently listening on that port.
In Production
In Prod, both Chrome and Firefox throw NET::ERR_CERT_AUTHORITY_INVALID while visiting the URL
Some stats, according to ssllabs.com:
Key: RSA 1024 bits (e 65537) WEAK
Certificate Transparency: No
DNS CAA: No
Trusted: No NOT TRUSTED (Why?)Mozilla Apple Android Java Windows
The text was updated successfully, but these errors were encountered: