发生了什么?
我正在尝试使用ollama在本地设置Quivr。已使用假的OPENAI_API_KEY和OLLAMA_API_BASE_URL更新了.env文件。
运行supabase start
后,我得到了一个错误状态502。
我位于企业防火墙后面。已设置环境变量http_proxy
和https_proxy
,并已配置docker守护进程+客户端使用代理。
相关日志输出:
Skipping migration local_20240107152745_ollama.sql... (file name must match pattern "<timestamp>_name.sql")
Applying migration 20240103173626_init.sql...
Applying migration 20240103175048_prod.sql...
Applying migration 20240103181249_premium.sql...
Applying migration 20240103181925_cleanup.sql...
Applying migration 20240103193921_stripe_customers.sql...
Applying migration 20240103194255_api.sql...
Applying migration 20240103204741_product_to_features.sql...
Applying migration 20240103231656_product.sql...
Applying migration 20240103234423_models.sql...
Applying migration 20240107231636_policies.sql...
Applying migration 20240119070124_search.sql...
Applying migration 20240119222036_metadata.sql...
Applying migration 20240120004107_tags.sql...
Applying migration 20240121195523_fix-public.sql...
Applying migration 20240122194117_monthly-credit.sql...
Applying migration 20240125230346_raw.sql...
Applying migration 20240206040636_notion.sql...
Applying migration 20240207034043_related.sql...
Applying migration 20240207071108_chunk.sql...
Applying migration 20240216192826_integration.sql...
Applying migration 20240228182948_notion.sql...
Applying migration 20240304223646_integrations-all.sql...
Applying migration 20240305225452_tags-integration.sql...
Applying migration 20240306013910_allow_model_change.sql...
Applying migration 20240306205133_integration_display_name.sql...
AApplying migration 20240313024244_onboarding-user.sql...
Applying migration 20240314005817_user_identity_company_info.sql...
Applying migration 20240316195514_usage_purpose.sql...
Applying migration 20240318024425_rename_feedback_to_thumbs.sql...
Applying migration 20240320215813_fix_match_vector_function.sql...
Applying migration 20240329212126_onboarding_brain.sql...
Applying migration 20240330233534_ingestion.sql...
Applying migration 20240402005455_ingestion.sql...
Applying migration 20240402013303_ingestion_url.sql...
Applying migration 20240402015128_seed-ingestions.sql...
Applying migration 20240410112108_assistant.sql...
Applying migration 20240501180719_notifications.sql...
Applying migration 20240506150059_timestampz.sql...
Applying migration 20240514080520_rls_optim.sql...
Applying migration 20240516143634_syncs.sql...
Applying migration 20240521144817_syncs-files.sql...
Applying migration 20240529132812_syncs-emails.sql...
Applying migration 20240606170930_sync-reduce-time.sql...
Applying migration 20240608095352_supported-sync.sql...
Applying migration 20240610141546_force-sync.sql...
Seeding data supabase/seed.sql...
supabase_edge_runtime_secondbrain container logs:
Download https://deno.land/std/http/status.ts
Download https://deno.land/x/jose@v4.13.1/index.ts
Stopping containers...
Error status 502:
Try rerunning the command with --debug to troubleshoot the error.
Twitter/LinkedIn详细信息:无响应
3条答案
按热度按时间monwx1rj1#
在运行
supabase start --debug
时出现错误日志(仅显示最后几部分,因为整个日志非常长)8qgya5xd2#
嘿 @chtanch! 我来帮助你解决任何问题或疑问。我是一个可以协助修复bug、回答问题并引导你成为贡献者的机器人。告诉我如何帮助你!
当你在企业防火墙后面运行
supabase start
时遇到的502 Bad Gateway错误很可能是由于网络配置问题,尤其是代理设置。以下是一些步骤来诊断和解决此问题:确保
http_proxy
和https_proxy
环境变量已正确设置。你可以通过运行以下命令来检查:确保Docker已配置为使用代理设置。你可以通过创建或编辑Docker守护进程配置文件(针对基于systemd的系统)来配置Docker以使用代理:
更改后,重启Docker:
确保Supabase CLI了解代理设置。在运行Supabase命令之前,你可以设置代理环境变量:
检查是否有可能会阻止Supabase所需的端口的网络限制或防火墙规则。确保以下端口已打开:
使用
--debug
标志运行 Supabase start 命令以获取更详细的日志:分析调试日志以识别任何特定的网络相关错误。
如果问题仍然存在,你可能需要咨询你的网络管理员,以确保所有必要的流量都允许通过企业防火墙。
f45qwnt83#
我已经检查了所有的解决方案步骤,它们并没有解决我的问题。