That's it... I think I understand you! ![]()
No problem - I use cerbot ![]()
ps: for me it makes no fundamental difference than receiving a ssl, because it does not solve the main problem
That's it... I think I understand you! ![]()
No problem - I use cerbot ![]()
ps: for me it makes no fundamental difference than receiving a ssl, because it does not solve the main problem
If you can run certbot directly, try adding that setting on the command line.
To solve that main problem, you need access to device:
OR to someone that can control it.
If I understand you correctly, then the problem is in the equipment and routing of my provider...
Thank you for your response!
the question can probably be closed
It is NOT routing; But, yes, the problem is within the equipment:
As mentioned before:
As proof of that, I mentioned that you could test with:
Which would show that your certbot is NOT part of the problem.
[and obtain a valid LE cert along the way]
I see the following line twice:
:::defconf drop invalid
I would like to know what mikrotik thinks about being "invalid". Could you extract this information, please?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.