Error parsing BASE_URL: no function clause matching in URI.parse/1 #1311
Answered
by
badsyntax
badsyntax
asked this question in
Self-Hosted Support
-
I'm using ~ $ /entrypoint.sh run
ERROR! Config provider Config.Reader failed with:
** (FunctionClauseError) no function clause matching in URI.parse/1
(elixir 1.11.3) lib/uri.ex:453: URI.parse({:ok, "https://plausible.docker-box.richardwillis.info/"})
(stdlib 3.14) erl_eval.erl:680: :erl_eval.do_apply/6
(stdlib 3.14) erl_eval.erl:449: :erl_eval.expr/5
(elixir 1.11.3) src/elixir.erl:280: :elixir.recur_eval/3
(elixir 1.11.3) src/elixir.erl:265: :elixir.eval_forms/3
(elixir 1.11.3) lib/code.ex:341: Code.eval_string_with_error_handling/3
(elixir 1.11.3) lib/config.ex:255: Config.__eval__!/3
(elixir 1.11.3) lib/config/reader.ex:86: Config.Reader.read!/2
{"init terminating in do_boot",{function_clause,[{'Elixir.URI',parse,[{ok,<<"https://plausible.docker-box.richardwillis.info/">>}],[{file,"lib/uri.ex"},{line,453}]},{erl_eval,do_apply,6,[{file,"erl_eval.erl"},{line,680}]},{erl_eval,expr,5,[{file,"erl_eval.erl"},{line,449}]},{elixir,recur_eval,3,[{file,"src/elixir.erl"},{line,280}]},{elixir,eval_forms,3,[{file,"src/elixir.erl"},{line,265}]},{'Elixir.Code',eval_string_with_error_handling,3,[{file,"lib/code.ex"},{line,341}]},{'Elixir.Config','__eval__!',3,[{file,"lib/config.ex"},{line,255}]},{'Elixir.Config.Reader','read!',2,[{file,"lib/config/reader.ex"},{line,86}]}]}}
init terminating in do_boot ({function_clause,[{Elixir.URI,parse,[{_}],[{_},{_}]},{erl_eval,do_apply,6,[{_},{_}]},{erl_eval,expr,5,[{_},{_}]},{elixir,recur_eval,3,[{_},{_}]},{elixir,eval_forms,3,[{_},
Crash dump is being written to: erl_crash.dump...done I could be wrong but it seems like it's failing here: Line 19 in 369f63b ... which doesn't make any sense. What am I doing wrong? The BASE_URL seems valid to me. |
Beta Was this translation helpful? Give feedback.
Answered by
badsyntax
Sep 9, 2021
Replies: 2 comments 2 replies
-
Do you have the trailing slash in your config? I believe that's the issue, if you remove it you should be good. |
Beta Was this translation helpful? Give feedback.
2 replies
-
The problem was a bug in plausible which is fixed with #1312 and available on |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
badsyntax
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem was a bug in plausible which is fixed with #1312 and available on
plausible/analytics:master