- 500 We’re sorry, but something went wrong. #36
- Comments
- Z3roCoder commented Jun 18, 2015
- Ablu commented Jun 30, 2015
- sameersbn commented Jul 1, 2015
- Z3roCoder commented Jul 8, 2015
- Z3roCoder commented Jul 8, 2015
- outcoldman commented Jul 8, 2015
- Z3roCoder commented Jul 8, 2015
- Z3roCoder commented Jul 8, 2015
- outcoldman commented Jul 8, 2015
- Z3roCoder commented Jul 9, 2015
- Z3roCoder commented Jul 9, 2015
- outcoldman commented Jul 9, 2015
- Z3roCoder commented Jul 9, 2015
- outcoldman commented Jul 9, 2015
- Z3roCoder commented Jul 10, 2015
- «We’re sorry, but something went wrong — If you are the application owner, check the logs for more informations». #981
- Comments
- djmuttart commented Jan 29, 2020
- «We’re sorry, but something went wrong.» in development mode #11063
- Comments
- istana commented Jun 23, 2013
- senny commented Jun 23, 2013
- istana commented Jun 23, 2013
- steveklabnik commented Jun 23, 2013
- istana commented Jun 24, 2013
- istana commented Jun 24, 2013
- steveklabnik commented Jun 25, 2013
- pixeltrix commented Jun 25, 2013
- senny commented Jun 25, 2013
- senny commented Jun 25, 2013
- cristianferrarig commented Oct 9, 2013
- printercu commented Jan 25, 2014
- Hussein1147 commented Mar 23, 2014
- Hussein1147 commented Mar 23, 2014
- Redmine
- Redmine won’t start (Ubuntu 14.04, redmine 3.1.2)
- Binance we re sorry but something went wrong
500 We’re sorry, but something went wrong. #36
Comments
Z3roCoder commented Jun 18, 2015
Why do I get this error? I have set everything up correctly according to https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/gitlab-ci/README.md yet I get this error. I have no idea what data to provide either so. Someone help please?
The text was updated successfully, but these errors were encountered:
Ablu commented Jun 30, 2015
I get this error too after I hit Login with GitLab and hitting Authorize on the dialog on the gitlab page.
sameersbn commented Jul 1, 2015
@Z3roCoder @Ablu Please refer to my comment #28 (comment) for a possible fix.
Z3roCoder commented Jul 8, 2015
None of any of those things helped.
Commands I am calling both docker-compose.yml’s with:
Z3roCoder commented Jul 8, 2015
outcoldman commented Jul 8, 2015
@Z3roCoder check the production.log,
Execute bash in your ci container (you can find the name with docker ps )
Go to the location of the logs
And check the production.log
Z3roCoder commented Jul 8, 2015
It always tells me «No route to host» — Did I set up something wrong in my files?
Z3roCoder commented Jul 8, 2015
outcoldman commented Jul 8, 2015
@Z3roCoder possible, I have never tried to set GITLAB_RELATIVE_URL_ROOT , maybe this can be an issue. Have you tried to curl from gitlabci server to the http://192.168.16.133:10080/gitlab to see if it actually has access to it? Also what is your callback url in gitlab?
Z3roCoder commented Jul 9, 2015
And where do I see what my Gitlab-Callback URL is?
@outcoldman
Z3roCoder commented Jul 9, 2015
(As it said «One URL per line» I thought you could enter multiple, as Gitlab and Gitlab-CI are supposed to work with ReverseProxies later)
@outcoldman
outcoldman commented Jul 9, 2015
@Z3roCoder you have the answer already — gitlab-ci does not have access to gitlab, when you tried to curl http://192.168.16.133:10080/gitlab it shows you No route to host . You need to fix that.
Z3roCoder commented Jul 9, 2015
Hmh, but how shall I do that? I can not use net: «host» or similar, and linking containers does not work either as when I link containers, the gitlab-url gets mapped to the hosts file, but an internal on elike «172.xxx.xxx.xxx» which I can not access on another computer. So letting the env GITLAB_URL get set automatically is no option either
outcoldman commented Jul 9, 2015
@Z3roCoder is http://192.168.16.133:10080/gitlab a url which you user in browser?
Z3roCoder commented Jul 10, 2015
Alright, I have now solved my problems. I have updated Docker as well as Docker-Compose to the newst Version and changed the following:
Источник
«We’re sorry, but something went wrong — If you are the application owner, check the logs for more informations». #981
Comments
djmuttart commented Jan 29, 2020
While logged into the Postal UI clicking the «queued messages» link results in a «We’re sorry, but something went wrong — If you are the application owner, check the logs for more informations».
The error from the rails.log is:
INFO — : Completed 500 Internal Server Error in 117ms (ActiveRecord: 51.2ms)
FATAL — :
FATAL — : ActionView::Template::Error (No message found matching provided query <:id=>90343>):
FATAL — : 1: %ul.messageList
2: — for message in messages
3: — if message.is_a?(QueuedMessage)
4: — message = message.message
5: %li.messageList__message
6: = link_to organization_server_message_path(organization, @server, message.id), :class => ‘messageList__link’ do
7: .messageList__details <:class =>‘messageList__details—‘ + message.scope>
FATAL — :
FATAL — : lib/postal/message_db/message.rb:13:in find_one’ lib/postal/message_db/database.rb:36:in message’
app/models/concerns/has_message.rb:8:in message’ app/views/messages/_list.html.haml:4:in block in _app_views_messages__list_html_haml__4169117333314457771_49077920′
app/views/messages/_list.html.haml:2:in each’ app/views/messages/_list.html.haml:2:in _app_views_messages__list_html_haml__4169117333314457771_49077920′
app/views/servers/queue.html.haml:21:in `_app_views_servers_queue_html_haml___1236125962400471721_70122255952860′
The text was updated successfully, but these errors were encountered:
Источник
«We’re sorry, but something went wrong.» in development mode #11063
Comments
istana commented Jun 23, 2013
But in development mode (log level is debug, all_requests_considered_local) it should display backtrace with informations.
Problem occurs when render is called fom controller or view and view (or partial) is misformatted (tested on slim, haml and erb) or somehow throws error. Does this with RC2 and master as well.
Whole log for request look like this:
The text was updated successfully, but these errors were encountered:
senny commented Jun 23, 2013
@istana can you please upload an isolated sample application to GitHub to reproduce the issue?
istana commented Jun 23, 2013
Finally I know why. problem is ‘ň’ in the path. I tried few non-acsii characters (ľ, á) and none worked. Also tried every combination of ruby 1.9.3, 2.0.0, rvm and rbenv.
I don’t know, if this is issue, but I thought Ruby (or Rails?) is UTF-8 compatible and behaviour is really weird.
@senny what do you think?
steveklabnik commented Jun 23, 2013
Make sure that your browser is properly escaping the character. Don’t trust the URI bar, check the logs.
I’m pretty sure this isn’t a bug.
istana commented Jun 24, 2013
Problem is related to filesystem path, not URIs. If application is located in /home/user/čosi/application it shows logs like in production mode while in development mode. If I rename it to /home/user/cosi/application it works just fine.
istana commented Jun 24, 2013
steveklabnik commented Jun 25, 2013
Ahhh. We have a ticket related to filepaths having a [ in it somewhere.
pixeltrix commented Jun 25, 2013
@steveklabnik #6010 but I think this is different — looks like it may be an encoding issue rather than a glob escaping issue.
senny commented Jun 25, 2013
I’ll take a look and report back.
senny commented Jun 25, 2013
I can confirm this is an encoding problem. It’s related to the backtrace generated when you have non-ascii characters in your file paths. Here is a simplified reproduction: https://gist.github.com/senny/5857653
cristianferrarig commented Oct 9, 2013
I had the same problem but only on some routes in the app.
In my case, this was because it had special characters in the respective controllers.
To fix this, I add at the beginning of each controller the next line
# encoding: utf-8
Sorry if this is not the best solution, but it worked for me. (for now)
printercu commented Jan 25, 2014
@senny, I have the same issue with slim templates and don’t have any special characters in file path. Haml’s SyntaxError and erb’s ActionView::Template::Error are rendered as usual. But with slim’s ActionView::Template::Error I get We’re sorry, but something went wrong. .
Hussein1147 commented Mar 23, 2014
hello I am having a somewhat similar issue in production mode, this is the same log i get
We’re sorry, but something went wrong.
If you are the application owner check the logs for more information.
My application works perfectly in development mode.
Hussein1147 commented Mar 23, 2014
in the server log there is this error
ActionController::RoutingError (No route matches [GET] «/»), but here is the whole log if that helps:
Источник
Redmine
Redmine won’t start (Ubuntu 14.04, redmine 3.1.2)
I’m trying to install redmine 3.1.2 on a virtual Ubuntu 14.04 (host windows).
I’ve use the tutorial HowTo Install Redmine 3.0.x on Ubuntu 14.04 with Apache2, Phusion Passenger, MySQL, Subversion and Git (Gitolite) and I had a problem with the following command:
bundle install —without development test postgresql sqlite
The command line was unable to be successful because there were a version conflict between «_gem ‘redcarpet’, ‘
> 3.1.2‘_» and «gem ‘redcarpet’, ‘
> 3.2.2‘». So I’ve changed, in opt/redmine/redmine-3.1.2/plugins/redmine_git_hosting, the line: «gem ‘redcarpet’, ‘
> 3.1.2′» into «gem ‘redcarpet’, ‘
Then I was able to continue installation. Installation works well (without error) until the end.
However, when I wanted to launch 127.0.0.1/redmine in firefox, I’ve firstly had an access denied error. So I’ve modified the access right to the passenger file with the command:
sudo chmod 644 /etc/apt/sources.list.d/passenger.list
Now, when I go to 127.0.0.1/redmine, I have no explicit message error, just the following message:
We’re sorry, but something went wrong.
We’ve been notified about this issue and we’ll take a look at it shortly.
Can someone tells me what I did wrong and how to resolve this?
Источник
Binance we re sorry but something went wrong
| Rname |
| ||
|
Загрузка .
| source777 |
| ||
 Эксперт Профиль Репутация: 12 | |||
|
| Rname |
| ||
| Цитата(source777 @ 20.4.2010, 11:53) |
| Ты видимо запустил сервер в production mode, запусти в development mode и тогда он покажет тебе описание твоей ошибки. |
  |  |
| Rname |
| ||
| Цитата(source777 @ 20.4.2010, 11:53) |
| Ты видимо запустил сервер в production mode, запусти в development mode и тогда он покажет тебе описание твоей ошибки. |
| | |
| source777 |
| |||
| Эксперт Профиль Репутация: 12
Что распаковал? Насколько я помню для работы с SQLite надо установить SQLite, а не распаковывать какие-то библиотеки во все возможные директории.
1) Юзать Linux. | ||||
|
| Rname |
| ||
Цитата(Rname @ 29.4.2010, 10:50  ) |
| Следуя советам всех, кто мне их давал, я распаковал во все возможные директории. |
Что распаковал? Насколько я помню для работы с SQLite надо установить SQLite, а не распаковывать какие-то библиотеки во все возможные директории.
| Цитата(Rname @ 29.4.2010, 10:50 ) |
| Как бытЬ? |
1) Юзать Linux.
2) Юзать MySQL
| | |
| source777 |
| ||||||||||||||
| Эксперт Профиль Репутация: 12
Ну если у тебя embedded база данных в каком-то десктопном приложении, то да. А для веб-приложений даже сложно представить зачем может понадобиться использовать SQLite.
| |||||||||||||||
