ValueError: list.remove(x): x not in list
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 25/100
- Tipo de issue
- Bug
- Clareza
- Precisa de esclarecimento
- Status de atividade
- Estagnada
- Stack de tecnologia
- python
- Domínio
- devops, infrastructure, security
Direção de pesquisa
Comece em /shared/letsencrypt/hook_script.py, em clean_challenge e na linha 62, e então reproduza a sequência completa de logs envolvendo os dois tokens de challenge. Compare os tokens registrados pela resposta ACME com os colocados na iRule de challenge e inspecione as regras do virtual server antes de cada limpeza. Está concluído quando as respostas ao challenge são bem-sucedidas e a limpeza é concluída sem o erro list.remove.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
I figure we'll start with what I believe is the main error and everything I'm using is what you have as current from March 21st :)
File "/shared/letsencrypt/hook_script.py", line 62, in clean_challenge
vip.properties['rules'].remove('/Common/le_challenge_rule')
ValueError: list.remove(x): x not in list
ERROR: clean_challenge hook returned with non-zero exit code
I see the files created on my Apache server using "watch ls" since it creates then removes them quickly. They did happen so that's working.
The iRule fails to delete per the error and it remains on the box. I've deleted it manually and re-run various times trying various things and still no luck.
I've commented out a few sections of the hook script and it still fails but it gives some insight. I'm not going to explain that now unless ya'll ask.
The other thing I'm seeing but this might be the issue w/ the iRule deletion failure.
The tokens seem to mismatch from what's in the log in the CLI vs. the token stored in the challenge iRule.
I can share most anything since this is my personal web server/F5.
Thoughts?
Here's a full log example below:
INFO: Using main config file /shared/letsencrypt/config
Processing projectbaiu.org with alternative names: www.projectbaiu.org
Signing domains...
Generating private key...
Generating signing request...
Requesting new certificate order from CA...
Received 2 authorizations URLs from the CA
Handling authorization for www.projectbaiu.org
Handling authorization for projectbaiu.org
2 pending challenge(s)
Deploying challenge tokens...
(hook) Deploying Challenge
(hook) Challenge rule added to virtual.
(hook) Deploying Challenge
(hook) Challenge rule added to virtual.
Responding to challenge for www.projectbaiu.org authorization...
(hook) Invalid Challenge
(hook) Invalid Challenge Args: ['www.projectbaiu.org', '["type"]\t"http-01"\n["status"]\t"invalid"\n["error","type"]\t"urn:ietf:params:acme:error:unauthorized"\n["error","detail"]\t"63.226.21.50: Invalid response from http://www.projectbaiu.org/.well-known/acme-challenge/oQL3Lr39uV-G-Bp4xq54VG4OQD7sexwc1uV2DmWsXHQ: 404"\n["error","status"]\t403\n["error"]\t{"type":"urn:ietf:params:acme:error:unauthorized","detail":"63.226.21.50: Invalid response from http://www.projectbaiu.org/.well-known/acme-challenge/oQL3Lr39uV-G-Bp4xq54VG4OQD7sexwc1uV2DmWsXHQ: 404","status":403}\n["url"]\t"https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2306706054/wc9l2A"\n["token"]\t"oQL3Lr39uV-G-Bp4xq54VG4OQD7sexwc1uV2DmWsXHQ"\n["validationRecord",0,"url"]\t"http://www.projectbaiu.org/.well-known/acme-challenge/oQL3Lr39uV-G-Bp4xq54VG4OQD7sexwc1uV2DmWsXHQ"\n["validationRecord",0,"hostname"]\t"www.projectbaiu.org"\n["validationRecord",0,"port"]\t"80"\n["validationRecord",0,"addressesResolved",0]\t"63.226.21.50"\n["validationRecord",0,"addressesResolved"]\t["63.226.21.50"]\n["validationRecord",0,"addressUsed"]\t"63.226.21.50"\n["validationRecord",0]\t{"url":"http://www.projectbaiu.org/.well-known/acme-challenge/oQL3Lr39uV-G-Bp4xq54VG4OQD7sexwc1uV2DmWsXHQ","hostname":"www.projectbaiu.org","port":"80","addressesResolved":["63.226.21.50"],"addressUsed":"63.226.21.50"}\n["validationRecord"]\t[{"url":"http://www.projectbaiu.org/.well-known/acme-challenge/oQL3Lr39uV-G-Bp4xq54VG4OQD7sexwc1uV2DmWsXHQ","hostname":"www.projectbaiu.org","port":"80","addressesResolved":["63.226.21.50"],"addressUsed":"63.226.21.50"}]\n["validated"]\t"2022-04-28T17:12:46Z"']
Cleaning challenge tokens...
(hook) Cleaning Challenge
(hook) Challenge rule removed from virtual.
(hook) Cleaning Challenge
Traceback (most recent call last):
File "/shared/letsencrypt/hook_script.py", line 120, in
clean_challenge(sys.argv[2:])
File "/shared/letsencrypt/hook_script.py", line 62, in clean_challenge
vip.properties['rules'].remove('/Common/le_challenge_rule')
ValueError: list.remove(x): x not in list
ERROR: clean_challenge hook returned with non-zero exit code
- Linguagem predominante
- Shell
- Estrelas
- 50
- Forks
- 12
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de f5devcentral/lets-encrypt-python
-
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 20/100
f5devcentral/lets-encrypt-python#10 · 1 comentário ·
-
Cert Chain ExistsTalvez livre de novo @f5-rahm assumiu há 1614 dias e não há nenhum pull request aberto. Aberta
f5devcentral/lets-encrypt-python#2 · 2 comentários · 1 responsável ·
Todas as issues de f5devcentral/lets-encrypt-python
Issues semelhantes
-
omarchy-menu-keybindings lua bind scan spins at 100% CPU when user config iterates a mocked hl APIAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
omacom/omarchy#14302 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Link Checker ReportTalvez já em andamento @keraron assumiu hoje. Abertaautomated issue report
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
a2aproject/A2A#2297 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
mattpocock/skills#1165 ·
-
agent-research-finding agent-research-recommend chore ready-for-agent
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
jordansmall/spindrift#4487 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
bigstack-oss/cubecos#1708 ·
Mantenedores costumam responder em até 1 dia