vercel部署出现问题 #77

Closed
opened 2026-02-21 17:25:53 -05:00 by yindo · 7 comments
Owner

Originally created by @dinggithub on GitHub (May 22, 2023).

fork之后进入vercel,点击import之后进入以下界面
112e27f1-1bb2-4386-bd2e-1f73b78e8397

点击deploy后是这样的,最后等了6分多钟都没有进行到下一步。请问是我哪里弄错了吗?
b73d7bac-7342-4e2c-a8d1-0269b6dc1f80

Originally created by @dinggithub on GitHub (May 22, 2023). fork之后进入vercel,点击import之后进入以下界面 ![112e27f1-1bb2-4386-bd2e-1f73b78e8397](https://github.com/langgenius/dify/assets/16711606/c448c287-994d-4f6e-85d6-88d81928e65c) 点击deploy后是这样的,最后等了6分多钟都没有进行到下一步。请问是我哪里弄错了吗? ![b73d7bac-7342-4e2c-a8d1-0269b6dc1f80](https://github.com/langgenius/dify/assets/16711606/c85bf539-0958-40ff-92c3-85ca7c5907a3)
yindo closed this issue 2026-02-21 17:25:53 -05:00
Author
Owner

@iamjoel commented on GitHub (May 22, 2023):

看看 vercel 的日志里有什么报错信息?

@iamjoel commented on GitHub (May 22, 2023): 看看 vercel 的日志里有什么报错信息?
Author
Owner

@dinggithub commented on GitHub (May 22, 2023):

source下面的是
54a6571 fix: extra input for opening statement was not suitable for prompt(#143)
image
以下是复制的All Logs:
[15:12:13.021] Running build in San Francisco, USA (West) – sfo1
[15:12:13.074] Cloning github.com/dinggithub/dify (Branch: main, Commit: 54a6571)
[15:12:13.222] Previous build cache not available
[15:12:14.142] Cloning completed: 1.065s
[15:12:14.484] Running "vercel build"
[15:12:15.136] Vercel CLI 29.3.6
[15:12:15.734] Installing required dependencies...
[15:12:17.909] Installing required dependencies...
[15:12:20.053] Installing required dependencies...
[15:12:22.040] Installing required dependencies...
[15:12:24.033] Installing required dependencies...
[15:12:25.969] Installing required dependencies...
[15:12:27.826] Installing required dependencies...
[15:12:29.717] Installing required dependencies...
[15:12:31.661] Installing required dependencies...
[15:12:33.641] Installing required dependencies...
[15:12:35.537] Installing required dependencies...
[15:12:37.453] Installing required dependencies...
[15:12:39.367] Installing required dependencies...
[15:12:41.290] Installing required dependencies...
[15:12:43.191] Installing required dependencies...
[15:12:45.041] Installing required dependencies...
[15:12:46.898] Installing required dependencies...
[15:12:48.819] Installing required dependencies...
[15:12:50.695] Installing required dependencies...
[15:12:52.589] Installing required dependencies...
[15:12:54.501] Installing required dependencies...
[15:12:56.417] Installing required dependencies...
[15:12:58.262] Installing required dependencies...
[15:13:00.149] Installing required dependencies...
[15:13:02.011] Installing required dependencies...
[15:13:03.860] Installing required dependencies...
[15:13:05.783] Installing required dependencies...
[15:13:07.743] Installing required dependencies...
[15:13:09.674] Installing required dependencies...
[15:13:11.624] Installing required dependencies...
[15:13:13.528] Installing required dependencies...
[15:13:15.421] Installing required dependencies...
[15:13:17.272] Installing required dependencies...
[15:13:19.150] Installing required dependencies...
[15:13:21.007] Installing required dependencies...
[15:13:22.876] Installing required dependencies...
[15:13:24.806] Installing required dependencies...
[15:13:26.656] Installing required dependencies...
[15:13:28.535] Installing required dependencies...
[15:13:30.462] Installing required dependencies...
[15:13:32.366] Installing required dependencies...
[15:13:34.247] Installing required dependencies...
[15:13:36.118] Installing required dependencies...
[15:13:37.972] Installing required dependencies...
[15:13:39.861] Installing required dependencies...
[15:13:41.811] Installing required dependencies...
[15:13:43.741] Installing required dependencies...
[15:13:45.607] Installing required dependencies...
[15:13:47.479] Installing required dependencies...
[15:13:49.341] Installing required dependencies...
[15:13:51.449] Installing required dependencies...
[15:13:53.351] Installing required dependencies...
[15:13:55.242] Installing required dependencies...
[15:13:57.110] Installing required dependencies...
[15:13:59.003] Installing required dependencies...
[15:14:00.907] Installing required dependencies...
[15:14:02.803] Installing required dependencies...
[15:14:04.716] Installing required dependencies...
[15:14:07.008] Installing required dependencies...
[15:14:09.183] Installing required dependencies...
[15:14:11.072] Installing required dependencies...
[15:14:13.020] Installing required dependencies...
[15:14:14.929] Installing required dependencies...
[15:14:16.815] Installing required dependencies...
[15:14:18.677] Installing required dependencies...
[15:14:20.530] Installing required dependencies...
[15:14:22.548] Installing required dependencies...
[15:14:24.577] Installing required dependencies...
[15:14:26.519] Installing required dependencies...
[15:14:28.387] Installing required dependencies...
[15:14:30.315] Installing required dependencies...
[15:14:32.165] Installing required dependencies...
[15:14:34.060] Installing required dependencies...
[15:14:35.896] Installing required dependencies...

@dinggithub commented on GitHub (May 22, 2023): source下面的是 54a6571 fix: extra input for opening statement was not suitable for prompt(#143) ![image](https://github.com/langgenius/dify/assets/16711606/a3302ef4-17b1-403a-8cdc-4f9fc395dbe1) 以下是复制的All Logs: [15:12:13.021] Running build in San Francisco, USA (West) – sfo1 [15:12:13.074] Cloning github.com/dinggithub/dify (Branch: main, Commit: 54a6571) [15:12:13.222] Previous build cache not available [15:12:14.142] Cloning completed: 1.065s [15:12:14.484] Running "vercel build" [15:12:15.136] Vercel CLI 29.3.6 [15:12:15.734] Installing required dependencies... [15:12:17.909] Installing required dependencies... [15:12:20.053] Installing required dependencies... [15:12:22.040] Installing required dependencies... [15:12:24.033] Installing required dependencies... [15:12:25.969] Installing required dependencies... [15:12:27.826] Installing required dependencies... [15:12:29.717] Installing required dependencies... [15:12:31.661] Installing required dependencies... [15:12:33.641] Installing required dependencies... [15:12:35.537] Installing required dependencies... [15:12:37.453] Installing required dependencies... [15:12:39.367] Installing required dependencies... [15:12:41.290] Installing required dependencies... [15:12:43.191] Installing required dependencies... [15:12:45.041] Installing required dependencies... [15:12:46.898] Installing required dependencies... [15:12:48.819] Installing required dependencies... [15:12:50.695] Installing required dependencies... [15:12:52.589] Installing required dependencies... [15:12:54.501] Installing required dependencies... [15:12:56.417] Installing required dependencies... [15:12:58.262] Installing required dependencies... [15:13:00.149] Installing required dependencies... [15:13:02.011] Installing required dependencies... [15:13:03.860] Installing required dependencies... [15:13:05.783] Installing required dependencies... [15:13:07.743] Installing required dependencies... [15:13:09.674] Installing required dependencies... [15:13:11.624] Installing required dependencies... [15:13:13.528] Installing required dependencies... [15:13:15.421] Installing required dependencies... [15:13:17.272] Installing required dependencies... [15:13:19.150] Installing required dependencies... [15:13:21.007] Installing required dependencies... [15:13:22.876] Installing required dependencies... [15:13:24.806] Installing required dependencies... [15:13:26.656] Installing required dependencies... [15:13:28.535] Installing required dependencies... [15:13:30.462] Installing required dependencies... [15:13:32.366] Installing required dependencies... [15:13:34.247] Installing required dependencies... [15:13:36.118] Installing required dependencies... [15:13:37.972] Installing required dependencies... [15:13:39.861] Installing required dependencies... [15:13:41.811] Installing required dependencies... [15:13:43.741] Installing required dependencies... [15:13:45.607] Installing required dependencies... [15:13:47.479] Installing required dependencies... [15:13:49.341] Installing required dependencies... [15:13:51.449] Installing required dependencies... [15:13:53.351] Installing required dependencies... [15:13:55.242] Installing required dependencies... [15:13:57.110] Installing required dependencies... [15:13:59.003] Installing required dependencies... [15:14:00.907] Installing required dependencies... [15:14:02.803] Installing required dependencies... [15:14:04.716] Installing required dependencies... [15:14:07.008] Installing required dependencies... [15:14:09.183] Installing required dependencies... [15:14:11.072] Installing required dependencies... [15:14:13.020] Installing required dependencies... [15:14:14.929] Installing required dependencies... [15:14:16.815] Installing required dependencies... [15:14:18.677] Installing required dependencies... [15:14:20.530] Installing required dependencies... [15:14:22.548] Installing required dependencies... [15:14:24.577] Installing required dependencies... [15:14:26.519] Installing required dependencies... [15:14:28.387] Installing required dependencies... [15:14:30.315] Installing required dependencies... [15:14:32.165] Installing required dependencies... [15:14:34.060] Installing required dependencies... [15:14:35.896] Installing required dependencies...
Author
Owner

@yuhao1118 commented on GitHub (May 22, 2023):

这个问题我也遇到了。首先,你应该选择web目录作为你的project root
image

其次,你可以参考 #127 提交的.env.example文件,配置好你的后端url地址。

我这样操作之后,页面是可以正常打开的,并且可以登录。但是我遇到了新的问题:

  1. 登录接口是请求成功的
  2. 登录之后的接口全部失败,报错是401
  3. 我理解是因为前后端是不同域名。session cookie的domain是后端域名,导致登录成功之后,后续的请求不会被带上cookie,导致接口请求失败
image image
@yuhao1118 commented on GitHub (May 22, 2023): 这个问题我也遇到了。首先,你应该选择web目录作为你的project root <img width="1424" alt="image" src="https://github.com/langgenius/dify/assets/26663836/3995cee1-c846-4aa5-8f69-585edbc5e1b9"> 其次,你可以参考 #127 提交的.env.example文件,配置好你的后端url地址。 我这样操作之后,页面是可以正常打开的,并且可以登录。但是我遇到了新的问题: 1. 登录接口是请求成功的 2. 登录之后的接口全部失败,报错是401 3. 我理解是因为前后端是不同域名。session cookie的domain是后端域名,导致登录成功之后,后续的请求不会被带上cookie,导致接口请求失败 <img width="739" alt="image" src="https://github.com/langgenius/dify/assets/26663836/70784ad1-a510-4b4f-8a7a-9701d8dc649e"> <img width="1674" alt="image" src="https://github.com/langgenius/dify/assets/26663836/767831ce-7cbd-4fc0-a63f-3889d95968ad">
Author
Owner

@yuhao1118 commented on GitHub (May 22, 2023):

这个问题我也遇到了。首先,你应该选择web目录作为你的project root image

其次,你可以参考 #127 提交的.env.example文件,配置好你的后端url地址。

我这样操作之后,页面是可以正常打开的,并且可以登录。但是我遇到了新的问题:

  1. 登录接口是请求成功的
  2. 登录之后的接口全部失败,报错是401
  3. 我理解是因为前后端是不同域名。session cookie的domain是后端域名,导致登录成功之后,后续的请求不会被带上cookie,导致接口请求失败

image image

破案了,api服务需要配置一下cookie跨站访问。如果是docker-compose启动的话,找到COOKIE_SAMESITE环境变量改成None。
image

@yuhao1118 commented on GitHub (May 22, 2023): > 这个问题我也遇到了。首先,你应该选择web目录作为你的project root <img alt="image" width="1424" src="https://user-images.githubusercontent.com/26663836/239909931-3995cee1-c846-4aa5-8f69-585edbc5e1b9.png"> > > 其次,你可以参考 #127 提交的.env.example文件,配置好你的后端url地址。 > > 我这样操作之后,页面是可以正常打开的,并且可以登录。但是我遇到了新的问题: > > 1. 登录接口是请求成功的 > 2. 登录之后的接口全部失败,报错是401 > 3. 我理解是因为前后端是不同域名。session cookie的domain是后端域名,导致登录成功之后,后续的请求不会被带上cookie,导致接口请求失败 > > <img alt="image" width="739" src="https://user-images.githubusercontent.com/26663836/239910868-70784ad1-a510-4b4f-8a7a-9701d8dc649e.png"> <img alt="image" width="1674" src="https://user-images.githubusercontent.com/26663836/239911619-767831ce-7cbd-4fc0-a63f-3889d95968ad.png"> 破案了,api服务需要配置一下cookie跨站访问。如果是docker-compose启动的话,找到COOKIE_SAMESITE环境变量改成None。 <img width="1019" alt="image" src="https://github.com/langgenius/dify/assets/26663836/1822dbc5-378f-4957-8e3f-7e56e4face15">
Author
Owner

@dinggithub commented on GitHub (May 22, 2023):

这个问题我也遇到了。首先,你应该选择web目录作为你的project root image
其次,你可以参考 #127 提交的.env.example文件,配置好你的后端url地址。
我这样操作之后,页面是可以正常打开的,并且可以登录。但是我遇到了新的问题:

  1. 登录接口是请求成功的
  2. 登录之后的接口全部失败,报错是401
  3. 我理解是因为前后端是不同域名。session cookie的domain是后端域名,导致登录成功之后,后续的请求不会被带上cookie,导致接口请求失败

image image

破案了,api服务需要配置一下cookie跨站访问。如果是docker-compose启动的话,找到COOKIE_SAMESITE环境变量改成None。 image

谢谢,第一个改web,我改了。
从这里开始“你可以参考 https://github.com/langgenius/dify/pull/127 提交的.env.example文件,配置好你的后端url地址。”我就不懂了。
技术小白,需要学习的东西太多了,我一点点研究,感谢!

@dinggithub commented on GitHub (May 22, 2023): > > 这个问题我也遇到了。首先,你应该选择web目录作为你的project root <img alt="image" width="1424" src="https://user-images.githubusercontent.com/26663836/239909931-3995cee1-c846-4aa5-8f69-585edbc5e1b9.png"> > > 其次,你可以参考 #127 提交的.env.example文件,配置好你的后端url地址。 > > 我这样操作之后,页面是可以正常打开的,并且可以登录。但是我遇到了新的问题: > > > > 1. 登录接口是请求成功的 > > 2. 登录之后的接口全部失败,报错是401 > > 3. 我理解是因为前后端是不同域名。session cookie的domain是后端域名,导致登录成功之后,后续的请求不会被带上cookie,导致接口请求失败 > > > > <img alt="image" width="739" src="https://user-images.githubusercontent.com/26663836/239910868-70784ad1-a510-4b4f-8a7a-9701d8dc649e.png"> <img alt="image" width="1674" src="https://user-images.githubusercontent.com/26663836/239911619-767831ce-7cbd-4fc0-a63f-3889d95968ad.png"> > > 破案了,api服务需要配置一下cookie跨站访问。如果是docker-compose启动的话,找到COOKIE_SAMESITE环境变量改成None。 <img alt="image" width="1019" src="https://user-images.githubusercontent.com/26663836/239912992-1822dbc5-378f-4957-8e3f-7e56e4face15.png"> 谢谢,第一个改web,我改了。 从这里开始“你可以参考 https://github.com/langgenius/dify/pull/127 提交的.env.example文件,配置好你的后端url地址。”我就不懂了。 技术小白,需要学习的东西太多了,我一点点研究,感谢!
Author
Owner

@Selenium39 commented on GitHub (Jul 27, 2023):

@yuhao1118 web可以部署到vercel,请问一下后端你是部署在什么平台呢?

@Selenium39 commented on GitHub (Jul 27, 2023): @yuhao1118 web可以部署到vercel,请问一下后端你是部署在什么平台呢?
Author
Owner

@xuanyuanbao commented on GitHub (Nov 1, 2023):

@yuhao1118 web可以部署到vercel,请问一下后端你是部署在什么平台呢?

同问,请问解决这个问题了吗

@xuanyuanbao commented on GitHub (Nov 1, 2023): > @yuhao1118 web可以部署到vercel,请问一下后端你是部署在什么平台呢? 同问,请问解决这个问题了吗
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#77